2012-05-31 18:00:34 +04:00
<?xml version="1.0"?>
<!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2023-08-22 19:52:02 +03:00
<refentry id= "systemd-modules-load.service" conditional= 'HAVE_KMOD'
xmlns:xi="http://www.w3.org/2001/XInclude">
2012-05-31 18:00:34 +04:00
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd-modules-load.service</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-modules-load.service</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-modules-load.service</refname>
<refname > systemd-modules-load</refname>
<refpurpose > Load kernel modules at boot</refpurpose>
</refnamediv>
<refsynopsisdiv >
<para > <filename > systemd-modules-load.service</filename> </para>
2015-06-18 20:47:44 +03:00
<para > <filename > /usr/lib/systemd/systemd-modules-load</filename> </para>
2015-02-04 05:14:13 +03:00
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2020-06-15 17:28:41 +03:00
<para > <filename > systemd-modules-load.service</filename> is an early boot service that loads kernel
2020-10-05 19:08:21 +03:00
modules. It reads static configuration from files in <filename > /usr/</filename> and
<filename > /etc/</filename> , but also runtime configuration from <filename > /run/</filename> and the kernel
2020-06-15 17:28:41 +03:00
command line (see below).</para>
2015-02-04 05:14:13 +03:00
<para > See
2020-06-15 17:28:41 +03:00
<citerefentry > <refentrytitle > modules-load.d</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> for
information about the configuration format of this service and paths where configuration files can be
created.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > Kernel Command Line</title>
<para > <filename > systemd-modules-load.service</filename>
understands the following kernel command line parameters:</para>
<variablelist class= 'kernel-commandline-options' >
<varlistentry >
util-lib: various improvements to kernel command line parsing
This improves kernel command line parsing in a number of ways:
a) An kernel option "foo_bar=xyz" is now considered equivalent to
"foo-bar-xyz", i.e. when comparing kernel command line option names "-" and
"_" are now considered equivalent (this only applies to the option names
though, not the option values!). Most of our kernel options used "-" as word
separator in kernel command line options so far, but some used "_". With
this change, which was a source of confusion for users (well, at least of
one user: myself, I just couldn't remember that it's systemd.debug-shell,
not systemd.debug_shell). Considering both as equivalent is inspired how
modern kernel module loading normalizes all kernel module names to use
underscores now too.
b) All options previously using a dash for separating words in kernel command
line options now use an underscore instead, in all documentation and in
code. Since a) has been implemented this should not create any compatibility
problems, but normalizes our documentation and our code.
c) All kernel command line options which take booleans (or are boolean-like)
have been reworked so that "foobar" (without argument) is now equivalent to
"foobar=1" (but not "foobar=0"), thus normalizing the handling of our
boolean arguments. Specifically this means systemd.debug-shell and
systemd_debug_shell=1 are now entirely equivalent.
d) All kernel command line options which take an argument, and where no
argument is specified will now result in a log message. e.g. passing just
"systemd.unit" will no result in a complain that it needs an argument. This
is implemented in the proc_cmdline_missing_value() function.
e) There's now a call proc_cmdline_get_bool() similar to proc_cmdline_get_key()
that parses booleans (following the logic explained in c).
f) The proc_cmdline_parse() call's boolean argument has been replaced by a new
flags argument that takes a common set of bits with proc_cmdline_get_key().
g) All kernel command line APIs now begin with the same "proc_cmdline_" prefix.
h) There are now tests for much of this. Yay!
2016-12-12 20:29:15 +03:00
<term > <varname > modules_load=</varname> </term>
<term > <varname > rd.modules_load=</varname> </term>
2015-02-04 05:14:13 +03:00
man: "the initial RAM disk" → "the initrd"
In many places we spelled out the phrase behind "initrd" in full, but this
isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this
is just confusing to the reader. Let's just say "initrd" everywhere, people
understand what this refers to, and that it's in fact an initramfs image.
Also, s/i.e./e.g./ where appropriate.
Also, don't say "in RAM", when in fact it's virtual memory, whose pages
may or may not be loaded in page frames in RAM, and we have no control over
this.
Also, add <filename></filename> and other minor cleanups.
2022-09-15 15:43:59 +03:00
<listitem > <para > Takes a comma-separated list of kernel modules to statically load during early boot.
2023-08-22 19:52:36 +03:00
The option prefixed with <literal > rd.</literal> is read in the initrd only.</para>
2023-09-18 18:03:38 +03:00
<xi:include href= "version-info.xml" xpointer= "v187" /> </listitem>
2015-02-04 05:14:13 +03:00
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > modules-load.d</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
</para>
</refsect1>
2012-05-31 18:00:34 +04:00
</refentry>
