morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00
Code Issues Packages Projects Releases Wiki Activity

tree-wide: use "_" rather than "-" as separator in kernel cmdline options

Browse Source 
Most of our kernel cmdline options use underscores as word separators in
kernel cmdline options, but there were some exceptions. Let's fix those,
and also use underscores.

Since our /proc/cmdline parsers don't distinguish between the two
characters anyway this should not break anything, but makes sure our own
codebase (and in particular docs and log messages) are internally
consistent.
This commit is contained in:
Lennart Poettering
2024-02-28 15:31:27 +01:00
parent 78816ce72e
commit 78266a54f1
18 changed files with 55 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
man/kernel-command-line.xml
View File

@@ -317,7 +317,7 @@
<term><varname>udev.blockdev_read_only</varname></term>
<term><varname>rd.udev.blockdev_read_only</varname></term>
<term><varname>net.ifnames=</varname></term>
<term><varname>net.naming-scheme=</varname></term>
<term><varname>net.naming_scheme=</varname></term>
<listitem>
<para>Parameters understood by the device event managing
@@ -609,7 +609,7 @@
<citerefentry><refentrytitle>systemd-homed-firstboot.service</refentrytitle><manvolnum>1</manvolnum></citerefentry>
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>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>
@@ -617,7 +617,7 @@
</varlistentry>
<varlistentry>
<term><varname>systemd.condition-needs-update=</varname></term>
<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
@@ -628,7 +628,7 @@
</varlistentry>
<varlistentry>
<term><varname>systemd.condition-first-boot=</varname></term>
<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
@@ -641,7 +641,7 @@
</varlistentry>
<varlistentry>
<term><varname>systemd.clock-usec=</varname></term>
<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
system clock to. The system time is set to the specified timestamp early during boot. It is not
@@ -651,7 +651,7 @@
</varlistentry>
<varlistentry>
<term><varname>systemd.random-seed=</varname></term>
<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