X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fmodules-load.d.xml;h=33c466f926b0ffb3b80a582f68f4ae417b37aae9;hp=47acc08e63541668822f24aa54c66d76b03fbe8b;hb=03ee5c38cb0da193dd08733fb4c0c2809cee6a99;hpb=a7c64469b68f442bcaaf771ac14a88c1b2a08b29 diff --git a/man/modules-load.d.xml b/man/modules-load.d.xml index 47acc08e6..33c466f92 100644 --- a/man/modules-load.d.xml +++ b/man/modules-load.d.xml @@ -4,22 +4,22 @@ - + modules-load.d @@ -47,40 +47,63 @@ /etc/modules-load.d/*.conf + /run/modules-load.d/*.conf + /usr/lib/modules-load.d/*.conf Description - systemd uses - /etc/modules-load.d/ 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 usally 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 modul names to load, seperated by - newlines. Empty lines and lines whose first - non-whitespace character is # or ; are ignored. - + 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. Example - /etc/modules-load.d/uinput.conf example: + /etc/modules-load.d/virtio-net.conf example: - # Load uinput.ko at boot -uinput + # Load virtio-net.ko at boot +virtio-net @@ -88,6 +111,8 @@ uinput See Also systemd1, + systemd-modules-load.service8, + systemd-delta1, modprobe8