X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fmodules-load.d.xml;h=34a937db68b6cfafedb3b547f1ab3539c3140368;hb=1c11181458990715e0ffd49e848baac5959e3c89;hp=01013e0222e8b95101436afd598373a4a05e43b3;hpb=7cf55dd0700d2b93f18a1bdc50b3c864d0af2246;p=elogind.git
diff --git a/man/modules-load.d.xml b/man/modules-load.d.xml
index 01013e022..34a937db6 100644
--- a/man/modules-load.d.xml
+++ b/man/modules-load.d.xml
@@ -19,94 +19,83 @@
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see .
-->
-
-
-
- modules-load.d
- systemd
-
-
-
- Developer
- Lennart
- Poettering
- lennart@poettering.net
-
-
-
-
-
- modules-load.d
- 5
-
-
-
- modules-load.d
- Configure kernel modules to load at boot
-
-
-
- /etc/modules-load.d/*.conf
- /run/modules-load.d/*.conf
- /usr/lib/modules-load.d/*.conf
-
-
-
- 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.
-
-
-
- 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.
-
-
-
- Example
-
- /etc/modules-load.d/virtio-net.conf example:
-
- # Load virtio-net.ko at boot
+
+
+
+ modules-load.d
+ systemd
+
+
+
+ Developer
+ Lennart
+ Poettering
+ lennart@poettering.net
+
+
+
+
+
+ modules-load.d
+ 5
+
+
+
+ modules-load.d
+ Configure kernel modules to load at boot
+
+
+
+ /etc/modules-load.d/*.conf
+ /run/modules-load.d/*.conf
+ /usr/lib/modules-load.d/*.conf
+
+
+
+ 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.
+
+
+
+ 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
+
+ /etc/modules-load.d/virtio-net.conf example:
+
+ # Load virtio-net.ko at boot
virtio-net
-
-
-
-
- See Also
-
- systemd1,
- modprobe8
-
-
+
+
+
+
+ See Also
+
+ systemd1,
+ systemd-modules-load.service8,
+ systemd-delta1,
+ modprobe8
+
+