X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fmodules-load.d.xml;h=33c466f926b0ffb3b80a582f68f4ae417b37aae9;hb=d1b6f12e07a304476ac29fc7306205f384db746f;hp=01013e0222e8b95101436afd598373a4a05e43b3;hpb=7cf55dd0700d2b93f18a1bdc50b3c864d0af2246;p=elogind.git
diff --git a/man/modules-load.d.xml b/man/modules-load.d.xml
index 01013e022..33c466f92 100644
--- a/man/modules-load.d.xml
+++ b/man/modules-load.d.xml
@@ -19,7 +19,7 @@
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see .
-->
-
+
modules-load.d
@@ -54,41 +54,47 @@
Description
- systemd uses
- files from the above directories to configure
- kernel modules to load during boot in a static list.
- Each configuration file is named in the style of
- /etc/modules-load.d/<program>.conf. Note
- that it is usually a better idea to use the automatic
- module loading by PCI ID, by DMI ID or similar
- triggers configured in the kernel modules themselves
- instead of relying on static configuration like
- this.
+ systemd-modules-load.service8
+ reads files from the above directories which contain
+ kernel modules to load during boot in a static list.
+ Each configuration file is named in the style of
+ /etc/modules-load.d/program.conf. Note
+ that it is usually a better idea to rely on the
+ automatic module loading by PCI IDs, USB IDs, DMI IDs
+ or similar triggers encoded in the kernel modules
+ themselves instead of static configuration like
+ this. In fact, most modern kernel modules are prepared
+ for automatic loading already.
- Configuration Format
-
- The configuration files should simply contain a
- list of kernel module names to load, separated by
- newlines. Empty lines and lines whose first
- non-whitespace character is # or ; are ignored.
-
- Each configuration file is named in the style of
- <program>.conf.
- Files in /etc/ override
- files with the same name in /usr/lib/.
- Files in /run override files with
- the same name in /etc/ and
- /usr/lib/. Packages should install their
- configuration files in /usr/lib/, files
- in /etc/ are reserved for the local
- administration, which possibly decides to override the
- configurations installed from packages. All files are sorted
- by filename in alphabetical order, regardless in which of the
- directories they reside, to ensure that a specific
- configuration file takes precedence over another file with
- an alphabetically later name.
+ Configuration Format
+
+ The configuration files should simply contain a
+ list of kernel module names to load, separated by
+ newlines. Empty lines and lines whose first
+ non-whitespace character is # or ; are ignored.
+
+ Each configuration file shall be named in the
+ style of program.conf.
+ Files in /etc/ override files
+ with the same name in /usr/lib/
+ and /run/. Files in
+ /run/ override files with the
+ same name in /usr/lib/. Packages
+ should install their configuration files in
+ /usr/lib/, files in
+ /etc/ are reserved for the local
+ administrator, who may use this logic to override the
+ configuration files installed from vendor
+ packages.
+
+ If the administrator wants to disable a
+ configuration file supplied by the vendor, the
+ recommended way is to place a symlink to
+ /dev/null in
+ /etc/modules-load.d/ bearing the
+ same filename.
@@ -105,6 +111,8 @@ virtio-net
See Also
systemd1,
+ systemd-modules-load.service8,
+ systemd-delta1,
modprobe8