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

man: mention "overlay" as a possible option for systemd.volatile

Browse Source 
systemd.volatile=overlay is described in the text below, however, it
is missing in the enclosed list of possible options in the beginning.
This commit is contained in:
Vitaly Kuznetsov
2025-04-07 17:45:54 +02:00
committed by Yu Watanabe
parent c019af5eed
commit f501830595
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -161,12 +161,12 @@
<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
directory and <filename>/var/</filename> are mounted as specified on the kernel command line or
<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
<filename>/usr/</filename> is mounted from the file system configured as root device, in read-only mode. This
enables fully state-less boots were the vendor-supplied OS is used as shipped, with only default
the special values <literal>state</literal> or <literal>overlay</literal>. If false (the default), normal boot
mode is selected, the root directory and <filename>/var/</filename> are mounted as specified on the kernel
command line or <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 <filename>/usr/</filename> is mounted from the file system configured as root device, in read-only mode.
This enables fully state-less boots were the vendor-supplied OS is used as shipped, with only default
configuration and no stored state in effect, as <filename>/etc/</filename> and <filename>/var/</filename> (as
well as all other resources shipped in the root file system) are reset at boot and lost on shutdown. If this
setting is set to <literal>state</literal> the root file system is mounted read-only, however