summaryrefslogtreecommitdiffstats
path: root/man/systemd-fstab-generator.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-10-05 18:08:21 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-10-05 18:44:05 +0200
commit3b1211574b0feeccb0d507b6f5db353d3a1a72c4 (patch)
treebbd4626f846b8bfa4bc01c907b6c6985434b9385 /man/systemd-fstab-generator.xml
parentman: add a note about flags on /tmp and /var/tmp (diff)
downloadsystemd-3b1211574b0feeccb0d507b6f5db353d3a1a72c4.tar.xz
systemd-3b1211574b0feeccb0d507b6f5db353d3a1a72c4.zip
man: use trailing slash on directories in more places
Diffstat (limited to 'man/systemd-fstab-generator.xml')
-rw-r--r--man/systemd-fstab-generator.xml28
1 files changed, 14 insertions, 14 deletions
diff --git a/man/systemd-fstab-generator.xml b/man/systemd-fstab-generator.xml
index 59f1896860..e842f3f9bc 100644
--- a/man/systemd-fstab-generator.xml
+++ b/man/systemd-fstab-generator.xml
@@ -110,7 +110,7 @@
<varlistentry>
<term><varname>mount.usr=</varname></term>
- <listitem><para>Takes the <filename>/usr</filename> filesystem
+ <listitem><para>Takes the <filename>/usr/</filename> filesystem
to be mounted by the initrd. If
<varname>mount.usrfstype=</varname> or
<varname>mount.usrflags=</varname> is set, then
@@ -118,7 +118,7 @@
<varname>root=</varname>.</para>
<para>Otherwise, this parameter defaults to the
- <filename>/usr</filename> entry found in
+ <filename>/usr/</filename> entry found in
<filename>/etc/fstab</filename> on the root filesystem.</para>
<para><varname>mount.usr=</varname> is honored by the initrd.
@@ -128,7 +128,7 @@
<varlistentry>
<term><varname>mount.usrfstype=</varname></term>
- <listitem><para>Takes the <filename>/usr</filename> filesystem
+ <listitem><para>Takes the <filename>/usr/</filename> filesystem
type that will be passed to the mount command. If
<varname>mount.usr=</varname> or
<varname>mount.usrflags=</varname> is set, then
@@ -136,7 +136,7 @@
set in <varname>rootfstype=</varname>.</para>
<para>Otherwise, this value will be read from the
- <filename>/usr</filename> entry in
+ <filename>/usr/</filename> entry in
<filename>/etc/fstab</filename> on the root filesystem.</para>
<para><varname>mount.usrfstype=</varname> is honored by the
@@ -146,14 +146,14 @@
<varlistentry>
<term><varname>mount.usrflags=</varname></term>
- <listitem><para>Takes the <filename>/usr</filename> filesystem
+ <listitem><para>Takes the <filename>/usr/</filename> filesystem
mount options to use. If <varname>mount.usr=</varname> or
<varname>mount.usrfstype=</varname> is set, then
<varname>mount.usrflags=</varname> will default to the value
set in <varname>rootflags=</varname>.</para>
<para>Otherwise, this value will be read from the
- <filename>/usr</filename> entry in
+ <filename>/usr/</filename> entry in
<filename>/etc/fstab</filename> on the root filesystem.</para>
<para><varname>mount.usrflags=</varname> is honored by the
@@ -173,15 +173,15 @@
<citerefentry><refentrytitle>systemd-volatile-root.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to
the host system, so that a volatile memory file system (<literal>tmpfs</literal>) is used as root directory,
- with only <filename>/usr</filename> mounted into it from the configured root file system, in read-only
+ with only <filename>/usr/</filename> mounted into it from the configured root file system, in read-only
mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and
- lost at shutdown, as <filename>/etc</filename> and <filename>/var</filename> will be served from the (initially
+ lost at shutdown, as <filename>/etc/</filename> and <filename>/var/</filename> will be served from the (initially
unpopulated) volatile memory file system.</para>
<para>If set to <option>state</option> the generator will leave the root directory mount point unaltered,
- however will mount a <literal>tmpfs</literal> file system to <filename>/var</filename>. In this mode the normal
- system configuration (i.e. the contents of <literal>/etc</literal>) is in effect (and may be modified during
- system runtime), however the system state (i.e. the contents of <literal>/var</literal>) is reset at boot and
+ however will mount a <literal>tmpfs</literal> file system to <filename>/var/</filename>. In this mode the normal
+ system configuration (i.e. the contents of <literal>/etc/</literal>) is in effect (and may be modified during
+ system runtime), however the system state (i.e. the contents of <literal>/var/</literal>) is reset at boot and
lost at shutdown.</para>
<para>If this setting is set to <literal>overlay</literal> the root file system is set up as
@@ -189,13 +189,13 @@
<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.</para>
- <para>Note that in none of these modes the root directory, <filename>/etc</filename>, <filename>/var</filename>
+ <para>Note that in none of these modes the root directory, <filename>/etc/</filename>, <filename>/var/</filename>
or any other resources stored in the root file system are physically removed. It's thus safe to boot a system
that is normally operated in non-volatile mode temporarily into volatile mode, without losing data.</para>
<para>Note that with the exception of <literal>overlay</literal> mode, enabling this setting will only work
- correctly on operating systems that can boot up with only <filename>/usr</filename> mounted, and are able to
- automatically populate <filename>/etc</filename>, and also <filename>/var</filename> in case of
+ correctly on operating systems that can boot up with only <filename>/usr/</filename> mounted, and are able to
+ automatically populate <filename>/etc/</filename>, and also <filename>/var/</filename> in case of
<literal>systemd.volatile=yes</literal>.</para></listitem>
</varlistentry>