X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fmodules-load.d.xml;h=4b578d714ce1f5996a3428c03447b3d68884b650;hb=48aae6d6a051acd9c0630fab1e79b82c847e538b;hp=cdd43d165097d5df3146680fc986e28afc710af6;hpb=9393a8774c1acd60deea40007061b9ffc783bf7e;p=elogind.git
diff --git a/man/modules-load.d.xml b/man/modules-load.d.xml
index cdd43d165..4b578d714 100644
--- a/man/modules-load.d.xml
+++ b/man/modules-load.d.xml
@@ -19,7 +19,8 @@
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see .
-->
-
+
modules-load.d
@@ -54,49 +55,30 @@
Description
- 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.
+ 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 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 file 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.
+
+
Example