56ba3c78ae
man rules were repeating the same information in too many places, which was error prone. Those rules can be easily generated from .xml files. For efficiency and because python is not a required dependency, Makefile-man.am is only regenerated when requested with make update-man-list If no metadata in man/*.xml changed, this file should not change. So only when a new man page or a new alias is added, this file should show up in 'git diff'. The change should then be committed. If the support for building from git without python was dropped, we could drop Makefile-man.am from version control. This would also increase the partial build time (since more stuff would be rebuild whenever sources in man/*.xml would be modified), so it would probably wouldn't be worth it.
121 lines
5.3 KiB
XML
121 lines
5.3 KiB
XML
<?xml version="1.0"?>
|
|
<!--*-nxml-*-->
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
<!--
|
|
This file is part of systemd.
|
|
|
|
Copyright 2011 Lennart Poettering
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
|
(at your option) any later version.
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
Lesser General Public License for more details.
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
-->
|
|
<refentry id="modules-load.d" conditional='HAVE_KMOD'>
|
|
|
|
<refentryinfo>
|
|
<title>modules-load.d</title>
|
|
<productname>systemd</productname>
|
|
|
|
<authorgroup>
|
|
<author>
|
|
<contrib>Developer</contrib>
|
|
<firstname>Lennart</firstname>
|
|
<surname>Poettering</surname>
|
|
<email>lennart@poettering.net</email>
|
|
</author>
|
|
</authorgroup>
|
|
</refentryinfo>
|
|
|
|
<refmeta>
|
|
<refentrytitle>modules-load.d</refentrytitle>
|
|
<manvolnum>5</manvolnum>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>modules-load.d</refname>
|
|
<refpurpose>Configure kernel modules to load at boot</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsynopsisdiv>
|
|
<para><filename>/etc/modules-load.d/*.conf</filename></para>
|
|
<para><filename>/run/modules-load.d/*.conf</filename></para>
|
|
<para><filename>/usr/lib/modules-load.d/*.conf</filename></para>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para><citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
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
|
|
<filename>/etc/modules-load.d/<program>.conf</filename>. 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.</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Configuration Format</title>
|
|
|
|
<para>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.</para>
|
|
|
|
<para>Each configuration file shall be named in the
|
|
style of <filename><program>.conf</filename>.
|
|
Files in <filename>/etc/</filename> override files
|
|
with the same name in <filename>/usr/lib/</filename>
|
|
and <filename>/run/</filename>. Files in
|
|
<filename>/run/</filename> override files with the
|
|
same name in <filename>/usr/lib/</filename>. Packages
|
|
should install their configuration files in
|
|
<filename>/usr/lib/</filename>, files in
|
|
<filename>/etc/</filename> are reserved for the local
|
|
administrator, who may use this logic to override the
|
|
configuration files installed from vendor
|
|
packages.</para>
|
|
|
|
<para>If the administrator wants to disable a
|
|
configuration file supplied by the vendor the
|
|
recommended way is to place a symlink to
|
|
<filename>/dev/null</filename> in
|
|
<filename>/etc/modules-load.d/</filename> bearing the
|
|
same file name.</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Example</title>
|
|
<example>
|
|
<title>/etc/modules-load.d/virtio-net.conf example:</title>
|
|
|
|
<programlisting># Load virtio-net.ko at boot
|
|
virtio-net</programlisting>
|
|
</example>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
<para>
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>systemd-delta</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>modprobe</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
</para>
|
|
</refsect1>
|
|
|
|
</refentry>
|