Debian Codegraph @

upstream/debian-unstable/man5/depmod.d.5

raw
1 .\" Generated by scdoc 1.11.4
2 .\" Complete documentation for this program is not available as a GNU info page
3 .ie \n(.g .ds Aq \(aq
4 .el .ds Aq '
5 .nh
6 .ad l
7 .\" Begin generated content:
8 .TH "DEPMOD.D" "5" "2026-04-26" "kmod" "depmod.d"
9 .PP
10 .SH NAME
11 .PP
12 depmod.\&d - Configuration directory for depmod
13 .PP
14 .SH SYNOPSIS
15 .PP
16 /etc/depmod.\&d/*.\&conf
17 .PP
18 /run/depmod.\&d/*.\&conf
19 .PP
20 /usr/local/lib/depmod.\&d/*.\&conf
21 .PP
22 /usr/lib/depmod.\&d/*.\&conf
23 .PP
24 /lib/depmod.\&d/*.\&conf
25 .PP
26 .SH DESCRIPTION
27 .PP
28 On execution \fBdepmod\fR reads the configuration files from the above location and
29 based on that it processes the available modules and their dependencies.\& For
30 example: one can change the search order, exclude folders, override specific
31 module'\&s location and more.\&
32 .PP
33 This is typically useful in cases where built-in kernel modules are complemented
34 by custom built versions of the same and the user wishes to affect the priority
35 of processing in order to override the module version supplied by the kernel.\&
36 .PP
37 .SH CONFIGURATION FORMAT
38 .PP
39 The configuration files contain one command per line, with blank lines and lines
40 starting with '\&#'\& ignored (useful for adding comments).\& A '\&\e'\& at the end of a
41 line causes it to continue on the next line, which makes the files a bit neater.\&
42 .PP
43 See the COMMANDS section below for more.\&
44 .PP
45 .SH CONFIGURATION DIRECTORIES AND PRECEDENCE
46 .PP
47 Configuration files are read from directories in listed in SYNOPSIS in that
48 order of precedence.\& Once a file of a given filename is loaded, any file of the
49 same name in subsequent directories is ignored.\&
50 .PP
51 All configuration files are sorted in lexicographic order, regardless of the
52 directory they reside in.\& Configuration files can either be completely replaced
53 (by having a new configuration file with the same name in a directory of higher
54 priority) or partially replaced (by having a configuration file that is ordered
55 later).\&
56 .PP
57 .SH COMMANDS
58 .PP
59 search \fIsubdirectory.\&.\&.\&\fR
60 .RS 4
61 This allows you to specify the order in which /lib/modules (or
62 other configured module location) subdirectories will be processed by
63 \fBdepmod\fR.\& Directories are listed in order, with the highest priority
64 given to the first listed directory and the lowest priority given to the
65 last directory listed.\& The special keyword \fBbuilt-in\fR refers to the
66 standard module directories installed by the kernel.\& Another special
67 keyword \fBexternal\fR refers to the list of external directories, defined
68 by the \fBexternal\fR command.\&
69 .PP
70 By default, depmod will give a higher priority to a directory with the
71 name \fBupdates\fR using this built-in search string: "updates built-in" but
72 more complex arrangements are possible and are used in several popular
73 distributions.\&
74 .PP
75 .RE
76 override \fImodulename\fR \fIkernelversion\fR \fImodulesubdirectory\fR
77 .RS 4
78 This command allows you to override which version of a specific module
79 will be used when more than one module sharing the same name is
80 processed by the \fBdepmod\fR command.\& It is possible to specify one kernel
81 or all kernels using the * wildcard.\& \fImodulesubdirectory\fR is the name
82 of the subdirectory under /lib/modules (or other module location)
83 where the target module is installed.\&
84 .PP
85 For example, it is possible to override the priority of an updated test
86 module called \fBkmod\fR by specifying the following command: "override
87 kmod * extra".\& This will ensure that any matching module name installed
88 under the \fBextra\fR subdirectory within /lib/modules (or other
89 module location) will take priority over any likenamed module already
90 provided by the kernel.\&
91 .PP
92 .RE
93 external \fIkernelversion\fR \fIabsolutemodulesdirectory.\&.\&.\&\fR
94 .RS 4
95 This specifies a list of directories, which will be checked according to
96 the priorities in the \fBsearch\fR command.\& The order matters also, the
97 first directory has the higher priority.\&
98 .PP
99 The \fIkernelversion\fR is a POSIX regular expression or * wildcard, like
100 in the \fBoverride\fR.\&
101 .PP
102 .RE
103 exclude \fIexcludedir\fR
104 .RS 4
105 This specifies the trailing directories that will be excluded during the
106 search for kernel modules.\&
107 .PP
108 The \fIexcludedir\fR is the trailing directory to exclude.\&
109 .PP
110 .RE
111 .SH COPYRIGHT
112 .PP
113 This manual page Copyright 2006-2010, Jon Masters, Red Hat, Inc.\&
114 .PP
115 .SH SEE ALSO
116 .PP
117 \fBdepmod\fR(8)
118 .PP
119 .SH BUGS
120 .PP
121 Please direct any bug reports to kmod'\&s issue tracker at
122 https://github.\&com/kmod-project/kmod/issues/ alongside with version used, steps
123 to reproduce the problem and the expected outcome.\&
124 .PP
125 .SH AUTHORS
126 .PP
127 Numerous contributions have come from the linux-modules mailing list
128 <linux-modules@vger.\&kernel.\&org> and Github.\& If you have a clone of kmod.\&git
129 itself, the output of \fBgit-shortlog\fR(1) and \fBgit-blame\fR(1) can show you the
130 authors for specific parts of the project.\&
131 .PP
132 \fBLucas De Marchi\fR <lucas.\&de.\&marchi@gmail.\&com> is the current maintainer of the
133 project.\&