From f5018305953725dffe6524a1a17cd018345b619c Mon Sep 17 00:00:00 2001
From: Vitaly Kuznetsov <vkuznets@redhat.com>
Date: Mon, 7 Apr 2025 17:45:54 +0200
Subject: [PATCH] man: mention "overlay" as a possible option for
 systemd.volatile

systemd.volatile=overlay is described in the text below, however, it
is missing in the enclosed list of possible options in the beginning.
---
 man/kernel-command-line.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/man/kernel-command-line.xml b/man/kernel-command-line.xml
index 17740fb4e45..a2a045d2090 100644
--- a/man/kernel-command-line.xml
+++ b/man/kernel-command-line.xml
@@ -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
-- 
2.47.3