Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   31170 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

MODULES-LOAD.D(5)		modules-load.d		     MODULES-LOAD.D(5)

NAME
       modules-load.d - Configure kernel modules to load at boot

SYNOPSIS
       /etc/modules-load.d/*.conf

       /run/modules-load.d/*.conf

       /usr/lib/modules-load.d/*.conf

DESCRIPTION
       systemd-modules-load.service(8) 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.

EXAMPLE
       Example 1. /etc/modules-load.d/virtio-net.conf example:

	   # Load virtio-net.ko at boot
	   virtio-net

SEE ALSO
       systemd(1), systemd-modules-load.service(8), systemd-delta(1),
       modprobe(8)

AUTHOR
       Lennart Poettering <lennart@poettering.net>
	   Developer

systemd				  02/15/2013		     MODULES-LOAD.D(5)

Vote for polarhome