2012-06-22 01:35:52 +02:00
|
|
|
<?xml version='1.0'?> <!--*-nxml-*-->
|
2019-03-14 14:40:58 +01:00
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
2015-06-18 19:47:44 +02:00
|
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
2020-11-09 05:23:58 +01:00
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2012-06-22 01:35:52 +02:00
|
|
|
|
|
|
|
|
<refentry id="kernel-command-line">
|
|
|
|
|
|
2015-02-04 03:14:13 +01:00
|
|
|
<refentryinfo>
|
|
|
|
|
<title>kernel-command-line</title>
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
<refentrytitle>kernel-command-line</refentrytitle>
|
|
|
|
|
<manvolnum>7</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
<refname>kernel-command-line</refname>
|
|
|
|
|
<refpurpose>Kernel command line parameters</refpurpose>
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
|
<para><filename>/proc/cmdline</filename></para>
|
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
2019-08-01 17:16:39 +02:00
|
|
|
<para>The kernel, the initial RAM disk (initrd) and basic userspace functionality may be configured at
|
|
|
|
|
boot via kernel command line arguments. In addition, various systemd tools look at the EFI variable
|
|
|
|
|
<literal>SystemdOptions</literal> (if available). Both sources are combined, but the kernel command line
|
|
|
|
|
has higher priority. Please note that <emphasis>the EFI variable is only used by systemd tools, and is
|
|
|
|
|
ignored by the kernel and other user space tools</emphasis>, so it is not a replacement for the kernel
|
|
|
|
|
command line.</para>
|
2015-02-04 03:14:13 +01:00
|
|
|
|
|
|
|
|
<para>For command line parameters understood by the kernel, please
|
2017-05-05 03:29:59 +02:00
|
|
|
see
|
|
|
|
|
<ulink url="https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html"><filename>kernel-parameters.html</filename></ulink>
|
2015-02-04 03:14:13 +01:00
|
|
|
and
|
|
|
|
|
<citerefentry project='man-pages'><refentrytitle>bootparam</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
|
|
|
|
|
|
|
|
|
|
<para>For command line parameters understood by the initial RAM
|
|
|
|
|
disk, please see
|
2015-11-05 15:38:19 +01:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>dracut.cmdline</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
2015-02-04 03:14:13 +01:00
|
|
|
or the documentation of the specific initrd implementation of your
|
|
|
|
|
installation.</para>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Core OS Command Line Arguments</title>
|
|
|
|
|
|
|
|
|
|
<variablelist class='kernel-commandline-options'>
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.unit=</varname></term>
|
|
|
|
|
<term><varname>rd.systemd.unit=</varname></term>
|
2017-02-20 02:02:12 +01:00
|
|
|
<term><varname>systemd.dump_core</varname></term>
|
2018-10-08 16:09:59 +02:00
|
|
|
<term><varname>systemd.early_core_pattern=</varname></term>
|
2017-02-20 02:02:12 +01:00
|
|
|
<term><varname>systemd.crash_chvt</varname></term>
|
|
|
|
|
<term><varname>systemd.crash_shell</varname></term>
|
|
|
|
|
<term><varname>systemd.crash_reboot</varname></term>
|
|
|
|
|
<term><varname>systemd.confirm_spawn</varname></term>
|
2017-03-20 13:10:43 +01:00
|
|
|
<term><varname>systemd.service_watchdogs</varname></term>
|
2017-02-20 02:02:12 +01:00
|
|
|
<term><varname>systemd.show_status</varname></term>
|
2019-06-06 19:22:20 +02:00
|
|
|
<term><varname>systemd.status_unit_format=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>systemd.log_target=</varname></term>
|
|
|
|
|
<term><varname>systemd.log_level=</varname></term>
|
|
|
|
|
<term><varname>systemd.log_location=</varname></term>
|
2017-02-20 02:02:12 +01:00
|
|
|
<term><varname>systemd.log_color</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>systemd.default_standard_output=</varname></term>
|
|
|
|
|
<term><varname>systemd.default_standard_error=</varname></term>
|
|
|
|
|
<term><varname>systemd.setenv=</varname></term>
|
2015-07-06 00:00:59 +02:00
|
|
|
<term><varname>systemd.machine_id=</varname></term>
|
2017-02-20 01:33:48 +01:00
|
|
|
<term><varname>systemd.unified_cgroup_hierarchy</varname></term>
|
|
|
|
|
<term><varname>systemd.legacy_systemd_cgroup_controller</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the system and service
|
|
|
|
|
manager to control system behavior. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.mask=</varname></term>
|
|
|
|
|
<term><varname>systemd.wants=</varname></term>
|
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 18:29:15 +01:00
|
|
|
<term><varname>systemd.debug_shell</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<listitem>
|
|
|
|
|
<para>Additional parameters understood by
|
|
|
|
|
<citerefentry><refentrytitle>systemd-debug-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
to mask or start specific units at boot, or invoke a debug
|
|
|
|
|
shell on tty9.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2018-11-16 12:15:50 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.run=</varname></term>
|
|
|
|
|
<term><varname>systemd.run_success_action=</varname></term>
|
|
|
|
|
<term><varname>systemd.run_failure_action=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Additional parameters understood by
|
|
|
|
|
<citerefentry><refentrytitle>systemd-run-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>, to
|
|
|
|
|
run a command line specified on the kernel command line as system service after booting up.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2018-10-08 16:09:59 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.early_core_pattern=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>During early boot, the generation of core dump files is disabled until a core dump handler (if any)
|
2019-12-24 13:50:04 +01:00
|
|
|
takes over. This parameter allows specifying an absolute path where core dump files should be stored until
|
2018-10-08 16:09:59 +02:00
|
|
|
a handler is installed. The path should be absolute and may contain specifiers, see
|
2020-06-25 14:37:24 +02:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>core</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para>
|
2018-10-08 16:09:59 +02:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 03:14:13 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.restore_state=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>This parameter is understood by several system tools
|
|
|
|
|
to control whether or not they should restore system state
|
|
|
|
|
from the previous boot. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-backlight@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
|
|
|
and
|
2015-11-05 15:38:19 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-rfkill.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
|
2015-02-04 03:14:13 +01:00
|
|
|
</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2016-12-13 12:45:19 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.volatile=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>This parameter controls whether the system shall boot up in volatile mode. Takes a boolean argument, or
|
|
|
|
|
the special value <literal>state</literal>. If false (the default), normal boot mode is selected, the root
|
2020-10-05 18:08:21 +02:00
|
|
|
directory and <filename>/var/</filename> are mounted as specified on the kernel command line or
|
2016-12-13 12:45:19 +01:00
|
|
|
<filename>/etc/fstab</filename>, or otherwise configured. If true, full state-less boot mode is selected. In
|
|
|
|
|
this case the root directory is mounted as volatile memory file system (<literal>tmpfs</literal>), and only
|
2020-10-05 18:08:21 +02:00
|
|
|
<filename>/usr/</filename> is mounted from the file system configured as root device, in read-only mode. This
|
2016-12-13 12:45:19 +01:00
|
|
|
enables fully state-less boots were the vendor-supplied OS is used as shipped, with only default
|
2020-10-05 18:08:21 +02:00
|
|
|
configuration and no stored state in effect, as <filename>/etc/</filename> and <filename>/var/</filename> (as
|
2016-12-13 12:45:19 +01:00
|
|
|
well as all other resources shipped in the root file system) are reset at boot and lost on shutdown. If this
|
2018-12-22 00:51:13 +01:00
|
|
|
setting is set to <literal>state</literal> the root file system is mounted read-only, however
|
2020-10-05 18:08:21 +02:00
|
|
|
<filename>/var/</filename> is mounted as a volatile memory file system (<literal>tmpfs</literal>), so that the
|
2018-12-22 00:51:13 +01:00
|
|
|
system boots up with the normal configuration applied, but all state reset at boot and lost at shutdown. If
|
|
|
|
|
this setting is set to <literal>overlay</literal> the root file system is set up as
|
|
|
|
|
<literal>overlayfs</literal> mount combining the read-only root directory with a writable
|
|
|
|
|
<literal>tmpfs</literal>, so that no modifications are made to disk, but the file system may be modified
|
|
|
|
|
nonetheless with all changes being lost at reboot. For details, see
|
2016-12-13 12:45:19 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-volatile-root.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
|
|
|
and
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 03:14:13 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>quiet</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameter understood by both the kernel and the system
|
|
|
|
|
and service manager to control console log verbosity. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>debug</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameter understood by both the kernel and the system
|
|
|
|
|
and service manager to control console log verbosity. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>-b</varname></term>
|
2016-06-13 16:28:42 +02:00
|
|
|
<term><varname>rd.emergency</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>emergency</varname></term>
|
2016-06-13 16:28:42 +02:00
|
|
|
<term><varname>rd.rescue</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>rescue</varname></term>
|
|
|
|
|
<term><varname>single</varname></term>
|
|
|
|
|
<term><varname>s</varname></term>
|
|
|
|
|
<term><varname>S</varname></term>
|
|
|
|
|
<term><varname>1</varname></term>
|
|
|
|
|
<term><varname>2</varname></term>
|
|
|
|
|
<term><varname>3</varname></term>
|
|
|
|
|
<term><varname>4</varname></term>
|
|
|
|
|
<term><varname>5</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the system and service
|
2016-06-13 16:28:42 +02:00
|
|
|
manager, as compatibility and convenience options. For details, see
|
2015-02-04 03:14:13 +01:00
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>locale.LANG=</varname></term>
|
|
|
|
|
<term><varname>locale.LANGUAGE=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_CTYPE=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_NUMERIC=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_TIME=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_COLLATE=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_MONETARY=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_MESSAGES=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_PAPER=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_NAME=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_ADDRESS=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_TELEPHONE=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_MEASUREMENT=</varname></term>
|
|
|
|
|
<term><varname>locale.LC_IDENTIFICATION=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the system and service
|
|
|
|
|
manager to control locale and language settings. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>fsck.mode=</varname></term>
|
|
|
|
|
<term><varname>fsck.repair=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the file system checker
|
|
|
|
|
services. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fsck@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>quotacheck.mode=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameter understood by the file quota checker
|
|
|
|
|
service. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-quotacheck.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.journald.forward_to_syslog=</varname></term>
|
|
|
|
|
<term><varname>systemd.journald.forward_to_kmsg=</varname></term>
|
|
|
|
|
<term><varname>systemd.journald.forward_to_console=</varname></term>
|
|
|
|
|
<term><varname>systemd.journald.forward_to_wall=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the journal service. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>vconsole.keymap=</varname></term>
|
2016-07-29 07:01:04 +02:00
|
|
|
<term><varname>vconsole.keymap_toggle=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>vconsole.font=</varname></term>
|
2016-07-29 07:01:04 +02:00
|
|
|
<term><varname>vconsole.font_map=</varname></term>
|
|
|
|
|
<term><varname>vconsole.font_unimap=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
|
|
|
|
|
<listitem>
|
2016-07-29 07:01:04 +02:00
|
|
|
<para>Parameters understood by the virtual console setup logic. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>vconsole.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
|
2015-02-04 03:14:13 +01:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
2020-09-21 11:10:50 +02:00
|
|
|
<term><varname>udev.log_level=</varname></term>
|
|
|
|
|
<term><varname>rd.udev.log_level=</varname></term>
|
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 18:29:15 +01:00
|
|
|
<term><varname>udev.children_max=</varname></term>
|
|
|
|
|
<term><varname>rd.udev.children_max=</varname></term>
|
|
|
|
|
<term><varname>udev.exec_delay=</varname></term>
|
|
|
|
|
<term><varname>rd.udev.exec_delay=</varname></term>
|
|
|
|
|
<term><varname>udev.event_timeout=</varname></term>
|
|
|
|
|
<term><varname>rd.udev.event_timeout=</varname></term>
|
2020-04-09 11:14:25 +02:00
|
|
|
<term><varname>udev.timeout_signal=</varname></term>
|
|
|
|
|
<term><varname>rd.udev.timeout_signal=</varname></term>
|
2020-06-02 15:15:24 +02:00
|
|
|
<term><varname>udev.blockdev_read_only</varname></term>
|
|
|
|
|
<term><varname>rd.udev.blockdev_read_only</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>net.ifnames=</varname></term>
|
2018-12-10 17:10:19 +01:00
|
|
|
<term><varname>net.naming-scheme=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Parameters understood by the device event managing
|
|
|
|
|
daemon. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>plymouth.enable=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>May be used to disable the Plymouth boot splash. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry project='die-net'><refentrytitle>plymouth</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>luks=</varname></term>
|
|
|
|
|
<term><varname>rd.luks=</varname></term>
|
|
|
|
|
<term><varname>luks.crypttab=</varname></term>
|
|
|
|
|
<term><varname>rd.luks.crypttab=</varname></term>
|
|
|
|
|
<term><varname>luks.name=</varname></term>
|
|
|
|
|
<term><varname>rd.luks.name=</varname></term>
|
|
|
|
|
<term><varname>luks.uuid=</varname></term>
|
|
|
|
|
<term><varname>rd.luks.uuid=</varname></term>
|
|
|
|
|
<term><varname>luks.options=</varname></term>
|
|
|
|
|
<term><varname>rd.luks.options=</varname></term>
|
|
|
|
|
<term><varname>luks.key=</varname></term>
|
|
|
|
|
<term><varname>rd.luks.key=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures the LUKS full-disk encryption logic at
|
|
|
|
|
boot. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>fstab=</varname></term>
|
|
|
|
|
<term><varname>rd.fstab=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures the <filename>/etc/fstab</filename> logic
|
|
|
|
|
at boot. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>root=</varname></term>
|
|
|
|
|
<term><varname>rootfstype=</varname></term>
|
2015-04-03 14:28:21 +02:00
|
|
|
<term><varname>rootflags=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
<term><varname>ro</varname></term>
|
|
|
|
|
<term><varname>rw</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures the root file system and its file system
|
|
|
|
|
type and mount options, as well as whether it shall be
|
2018-12-20 16:09:48 +01:00
|
|
|
mounted read-only or read-write initially. For details,
|
2015-02-04 03:14:13 +01:00
|
|
|
see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2017-09-05 12:25:56 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>mount.usr=</varname></term>
|
|
|
|
|
<term><varname>mount.usrfstype=</varname></term>
|
|
|
|
|
<term><varname>mount.usrflags=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures the /usr file system (if required) and
|
|
|
|
|
its file system type and mount options. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2016-12-16 12:57:44 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>roothash=</varname></term>
|
|
|
|
|
<term><varname>systemd.verity=</varname></term>
|
|
|
|
|
<term><varname>rd.systemd.verity=</varname></term>
|
|
|
|
|
<term><varname>systemd.verity_root_data=</varname></term>
|
|
|
|
|
<term><varname>systemd.verity_root_hash=</varname></term>
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures the integrity protection root hash for the root file system, and other related
|
|
|
|
|
parameters. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-veritysetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 03:14:13 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.gpt_auto=</varname></term>
|
|
|
|
|
<term><varname>rd.systemd.gpt_auto=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Configures whether GPT based partition auto-discovery
|
|
|
|
|
shall be attempted. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2016-04-26 17:10:36 +02:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.default_timeout_start_sec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Overwrites the default start job timeout <varname>DefaultTimeoutStartSec=</varname> at boot. For details,
|
|
|
|
|
see <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
|
2017-12-08 18:27:01 +01:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.watchdog_device=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Overwrites the watchdog device path <varname>WatchdogDevice=</varname>. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
|
2016-04-26 17:10:36 +02:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2019-11-26 09:46:00 +01:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.cpu_affinity=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Overrides the CPU affinity mask for the service manager and the default for all child
|
|
|
|
|
processes it forks. This takes precedence over <varname>CPUAffinity=</varname>, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for details.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
2015-02-04 03:14:13 +01:00
|
|
|
<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 18:29:15 +01:00
|
|
|
<term><varname>modules_load=</varname></term>
|
|
|
|
|
<term><varname>rd.modules_load=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Load a specific kernel module early at boot. For
|
|
|
|
|
details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>resume=</varname></term>
|
2019-06-06 02:59:05 +02:00
|
|
|
<term><varname>resumeflags=</varname></term>
|
2015-02-04 03:14:13 +01:00
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Enables resume from hibernation using the specified
|
2019-06-06 02:59:05 +02:00
|
|
|
device and mount options. All
|
2015-03-14 03:22:39 +01:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>-like
|
2015-02-04 03:14:13 +01:00
|
|
|
paths are supported. For details, see
|
|
|
|
|
<citerefentry><refentrytitle>systemd-hibernate-resume-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
2016-12-09 01:11:42 +01:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.firstboot=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a boolean argument, defaults to on. If off,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-firstboot.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
2020-05-14 10:11:56 +02:00
|
|
|
will not query the user for basic system settings, even if the system boots up for the first time and
|
|
|
|
|
the relevant settings are not initialized yet. Not to be confused with
|
|
|
|
|
<varname>systemd.condition-first-boot=</varname> (see below), which overrides the result of the
|
|
|
|
|
<varname>ConditionFirstBoot=</varname> unit file condition, and thus controls more than just
|
|
|
|
|
<filename>systemd-firstboot.service</filename> behaviour.</para></listitem>
|
2016-12-09 01:11:42 +01:00
|
|
|
</varlistentry>
|
2020-05-14 09:55:57 +02:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.condition-needs-update=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a boolean argument. If specified, overrides the result of
|
|
|
|
|
<varname>ConditionNeedsUpdate=</varname> unit condition checks. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
|
|
|
|
|
details.</para></listitem>
|
|
|
|
|
</varlistentry>
|
2020-05-14 10:11:56 +02:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.condition-first-boot=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a boolean argument. If specified, overrides the result of
|
|
|
|
|
<varname>ConditionFirstBoot=</varname> unit condition checks. See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
|
|
|
|
|
details. Not to be confused with <varname>systemd.firstboot=</varname> which only controls behaviour
|
|
|
|
|
of the <filename>systemd-firstboot.service</filename> system service but has no effect on the
|
|
|
|
|
condition check (see above).</para></listitem>
|
|
|
|
|
</varlistentry>
|
2020-05-14 10:41:47 +02:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.clock-usec=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a decimal, numeric timestamp in µs since January 1st 1970, 00:00am, to set the
|
2020-06-11 10:04:41 +02:00
|
|
|
system clock to. The system time is set to the specified timestamp early during boot. It is not
|
|
|
|
|
propagated to the hardware clock (RTC).</para></listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.random-seed=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes a base64 encoded random seed value to credit with full entropy to the kernel's
|
|
|
|
|
random pool during early service manager initialization. This option is useful in testing
|
|
|
|
|
environments where delays due to random pool initialization in entropy starved virtual machines shall
|
|
|
|
|
be avoided.</para>
|
|
|
|
|
|
|
|
|
|
<para>Note that if this option is used the seed is accessible to unprivileged programs from
|
|
|
|
|
<filename>/proc/cmdline</filename>. This option is hence a security risk when used outside of test
|
|
|
|
|
systems, since the (possibly) only seed used for initialization of the kernel's entropy pool might be
|
|
|
|
|
easily acquired by unprivileged programs.</para>
|
|
|
|
|
|
|
|
|
|
<para>It is recommended to pass 512 bytes of randomized data (as that matches the Linux kernel pool
|
|
|
|
|
size), which may be generated with a command like the following:</para>
|
|
|
|
|
|
|
|
|
|
<programlisting>dd if=/dev/urandom bs=512 count=1 status=none | base64 -w 0</programlisting>
|
|
|
|
|
|
|
|
|
|
<para>Again: do not use this option outside of testing environments, it's a security risk elsewhere,
|
|
|
|
|
as secret key material derived from the entropy pool can possibly be reconstructed by unprivileged
|
|
|
|
|
programs.</para>
|
|
|
|
|
</listitem>
|
2020-05-14 10:41:47 +02:00
|
|
|
</varlistentry>
|
2020-05-14 11:01:31 +02:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.hostname=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Accepts a hostname to set during early boot. If specified takes precedence over what
|
|
|
|
|
is set in <filename>/etc/hostname</filename>. Note that this does not bar later runtime changes to
|
|
|
|
|
the hostname, it simply controls the initial hostname set during early boot.</para></listitem>
|
|
|
|
|
</varlistentry>
|
2015-02-04 03:14:13 +01:00
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
|
|
|
|
<para>
|
|
|
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
2019-02-01 12:31:51 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
2015-02-04 03:14:13 +01:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>bootparam</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
2015-11-05 15:38:19 +01:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>dracut.cmdline</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
|
2015-02-04 03:14:13 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-debug-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-fsck@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-quotacheck.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-vconsole-setup.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry project='die-net'><refentrytitle>plymouth</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2016-12-16 12:57:44 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-veritysetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2015-02-04 03:14:13 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2016-12-13 12:45:19 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-volatile-root.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2015-02-04 03:14:13 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>systemd-backlight@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2015-11-05 15:38:19 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-rfkill.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2016-12-09 01:11:42 +01:00
|
|
|
<citerefentry><refentrytitle>systemd-hibernate-resume-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
2019-08-01 17:15:59 +02:00
|
|
|
<citerefentry><refentrytitle>systemd-firstboot.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
|
|
|
<citerefentry><refentrytitle>bootctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
|
2015-02-04 03:14:13 +01:00
|
|
|
</para>
|
|
|
|
|
</refsect1>
|
2012-06-22 01:35:52 +02:00
|
|
|
|
|
|
|
|
</refentry>
|