1MODULES-LOAD.D(5)               modules-load.d               MODULES-LOAD.D(5)
2
3
4

NAME

6       modules-load.d - Configure kernel modules to load at boot
7

SYNOPSIS

9       /etc/modules-load.d/*.conf
10
11       /run/modules-load.d/*.conf
12
13       /usr/lib/modules-load.d/*.conf
14

DESCRIPTION

16       systemd-modules-load.service(8) reads files from the above directories
17       which contain kernel modules to load during boot in a static list. Each
18       configuration file is named in the style of
19       /etc/modules-load.d/program.conf. Note that it is usually a better idea
20       to rely on the automatic module loading by PCI IDs, USB IDs, DMI IDs or
21       similar triggers encoded in the kernel modules themselves instead of
22       static configuration like this. In fact, most modern kernel modules are
23       prepared for automatic loading already.
24

CONFIGURATION FORMAT

26       The configuration files should simply contain a list of kernel module
27       names to load, separated by newlines. Empty lines and lines whose first
28       non-whitespace character is # or ; are ignored.
29

CONFIGURATION DIRECTORIES AND PRECEDENCE

31       Configuration files are read from directories in /etc/, /run/,
32       /usr/local/lib/, and /usr/lib/, in order of precedence. Each
33       configuration file in these configuration directories shall be named in
34       the style of filename.conf. Files in /etc/ override files with the same
35       name in /run/, /usr/local/lib/, and /usr/lib/. Files in /run/ override
36       files with the same name under /usr/.
37
38       Packages should install their configuration files in /usr/lib/
39       (distribution packages) or /usr/local/lib/ (local installs). Files in
40       /etc/ are reserved for the local administrator, who may use this logic
41       to override the configuration files installed by vendor packages. All
42       configuration files are sorted by their filename in lexicographic
43       order, regardless of which of the directories they reside in. If
44       multiple files specify the same option, the entry in the file with the
45       lexicographically latest name will take precedence. It is recommended
46       to prefix all filenames with a two-digit number and a dash, to simplify
47       the ordering of the files.
48
49       If the administrator wants to disable a configuration file supplied by
50       the vendor, the recommended way is to place a symlink to /dev/null in
51       the configuration directory in /etc/, with the same filename as the
52       vendor configuration file. If the vendor configuration file is included
53       in the initrd image, the image has to be regenerated.
54

EXAMPLE

56       Example 1. /etc/modules-load.d/virtio-net.conf example:
57
58           # Load virtio-net.ko at boot
59           virtio-net
60

SEE ALSO

62       systemd(1), systemd-modules-load.service(8), systemd-delta(1),
63       modprobe(8)
64
65
66
67systemd 243                                                  MODULES-LOAD.D(5)
Impressum