2012-06-27 13:27:29 +00:00
|
|
|
<?xml version="1.0"?>
|
|
|
|
|
<!--*-nxml-*-->
|
2019-03-14 13:40:58 +00:00
|
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
2023-12-25 14:48:33 +00:00
|
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
|
2020-11-09 04:23:58 +00:00
|
|
|
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
|
2023-08-22 16:52:02 +00:00
|
|
|
<refentry id="systemd-fstab-generator" xmlns:xi="http://www.w3.org/2001/XInclude">
|
2012-06-27 13:27:29 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<refentryinfo>
|
|
|
|
|
<title>systemd-fstab-generator</title>
|
|
|
|
|
<productname>systemd</productname>
|
|
|
|
|
</refentryinfo>
|
|
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
|
<refentrytitle>systemd-fstab-generator</refentrytitle>
|
|
|
|
|
<manvolnum>8</manvolnum>
|
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
|
<refname>systemd-fstab-generator</refname>
|
|
|
|
|
<refpurpose>Unit generator for /etc/fstab</refpurpose>
|
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
2015-06-18 17:47:44 +00:00
|
|
|
<para><filename>/usr/lib/systemd/system-generators/systemd-fstab-generator</filename></para>
|
2015-02-04 02:14:13 +00:00
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
|
|
<para><filename>systemd-fstab-generator</filename> is a generator
|
|
|
|
|
that translates <filename>/etc/fstab</filename> (see
|
2015-03-14 02:22:39 +00:00
|
|
|
<citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
2015-02-04 02:14:13 +00:00
|
|
|
for details) into native systemd units early at boot and when
|
|
|
|
|
configuration of the system manager is reloaded. This will
|
|
|
|
|
instantiate mount and swap units as necessary.</para>
|
|
|
|
|
|
|
|
|
|
<para>The <varname>passno</varname> field is treated like a simple
|
|
|
|
|
boolean, and the ordering information is discarded. However, if
|
|
|
|
|
the root file system is checked, it is checked before all the
|
|
|
|
|
other file systems.</para>
|
|
|
|
|
|
|
|
|
|
<para>See
|
|
|
|
|
<citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
and
|
|
|
|
|
<citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
|
|
|
|
for more information about special <filename>/etc/fstab</filename>
|
|
|
|
|
mount options this generator understands.</para>
|
|
|
|
|
|
2022-07-14 11:29:06 +00:00
|
|
|
<para>One special topic is handling of symbolic links. Historical init
|
fstab-generator: Chase symlinks where possible (#6293)
This has a long history; see see 5261ba901845c084de5a8fd06500ed09bfb0bd80
which originally introduced the behavior. Unfortunately that commit
doesn't include any rationale, but IIRC the basic issue is that
systemd wants to model the real mount state as units, and symlinks
make canonicalization much more difficult.
At the same time, on a RHEL6 system (upstart), one can make e.g. `/home` a
symlink, and things work as well as they always did; but one doesn't have
access to the sophistication of mount units (dependencies, introspection, etc.)
Supporting symlinks here will hence make it easier for people to do upgrades to
RHEL7 and beyond.
The `/home` as symlink case also appears prominently for OSTree; see
https://ostree.readthedocs.io/en/latest/manual/adapting-existing/
Further work has landed in the nspawn case for this; see e.g.
d944dc9553009822deaddec76814f5642a6a8176
A basic limitation with doing this in the fstab generator (and that I hit while
doing some testing) is that we obviously can't chase symlinks into mounts,
since the generator runs early before mounts. Or at least - doing so would
require multiple passes over the fstab data (as well as looking at existing
mount units), and potentially doing multi-phase generation. I'm not sure it's
worth doing that without a real world use case. For now, this will fix at least
the OSTree + `/home` <https://bugzilla.redhat.com/show_bug.cgi?id=1382873> case
mentioned above, and in general anyone who for whatever reason has symlinks in
their `/etc/fstab`.
2017-07-11 16:48:57 +00:00
|
|
|
implementations supported symlinks in <filename>/etc/fstab</filename>.
|
|
|
|
|
Because mount units will refuse mounts where the target is a symbolic link,
|
|
|
|
|
this generator will resolve any symlinks as far as possible when processing
|
|
|
|
|
<filename>/etc/fstab</filename> in order to enhance backwards compatibility.
|
|
|
|
|
If a symlink target does not exist at the time that this generator runs, it
|
|
|
|
|
is assumed that the symlink target is the final target of the mount.</para>
|
|
|
|
|
|
2015-03-04 23:43:20 +00:00
|
|
|
<para><filename>systemd-fstab-generator</filename> implements
|
|
|
|
|
<citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
|
2015-02-04 02:14:13 +00:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
|
<title>Kernel Command Line</title>
|
|
|
|
|
|
|
|
|
|
<para><filename>systemd-fstab-generator</filename> understands the
|
|
|
|
|
following kernel command line parameters:</para>
|
|
|
|
|
|
|
|
|
|
<variablelist class='kernel-commandline-options'>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>fstab=</varname></term>
|
|
|
|
|
<term><varname>rd.fstab=</varname></term>
|
|
|
|
|
|
man: "the initial RAM disk" → "the initrd"
In many places we spelled out the phrase behind "initrd" in full, but this
isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this
is just confusing to the reader. Let's just say "initrd" everywhere, people
understand what this refers to, and that it's in fact an initramfs image.
Also, s/i.e./e.g./ where appropriate.
Also, don't say "in RAM", when in fact it's virtual memory, whose pages
may or may not be loaded in page frames in RAM, and we have no control over
this.
Also, add <filename></filename> and other minor cleanups.
2022-09-15 12:43:59 +00:00
|
|
|
<listitem><para>Takes a boolean argument. Defaults to <literal>yes</literal>. If
|
|
|
|
|
<literal>no</literal>, causes the generator to ignore any mounts or swap devices configured in
|
|
|
|
|
<filename>/etc/fstab</filename>. <varname>rd.fstab=</varname> is honored only in the initrd, while
|
2023-08-22 16:52:36 +00:00
|
|
|
<varname>fstab=</varname> is honored by both the main system and the initrd.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>root=</varname></term>
|
|
|
|
|
|
2021-03-02 17:57:04 +00:00
|
|
|
<listitem><para>Configures the operating system's root filesystem to mount when running in the
|
|
|
|
|
initrd. This accepts a device node path (usually <filename>/dev/disk/by-uuid/…</filename> or
|
2023-01-26 00:05:08 +00:00
|
|
|
<filename>/dev/disk/by-label/…</filename> or similar), or the special values <literal>gpt-auto</literal>,
|
|
|
|
|
<literal>fstab</literal>, and <literal>tmpfs</literal>.</para>
|
2021-03-02 17:57:04 +00:00
|
|
|
|
|
|
|
|
<para>Use <literal>gpt-auto</literal> to explicitly request automatic root file system discovery via
|
|
|
|
|
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
|
2023-01-26 00:05:08 +00:00
|
|
|
<para>Use <literal>fstab</literal> to explicitly request automatic root file system discovery via
|
|
|
|
|
the initrd <filename>/etc/fstab</filename> rather than via kernel command line.</para>
|
|
|
|
|
|
2021-03-02 17:57:04 +00:00
|
|
|
<para>Use <literal>tmpfs</literal> in order to mount a <citerefentry
|
|
|
|
|
project='man-pages'><refentrytitle>tmpfs</refentrytitle><manvolnum>5</manvolnum></citerefentry> file
|
|
|
|
|
system as root file system of the OS. This is useful in combination with
|
|
|
|
|
<varname>mount.usr=</varname> (see below) in order to combine a volatile root file system with a
|
|
|
|
|
separate, immutable <filename>/usr/</filename> file system. Also see
|
2023-08-22 16:52:36 +00:00
|
|
|
<varname>systemd.volatile=</varname> below.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>rootfstype=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Takes the root filesystem type that will be
|
|
|
|
|
passed to the mount command. <varname>rootfstype=</varname> is
|
2023-08-22 16:52:36 +00:00
|
|
|
honored by the initrd.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>rootflags=</varname></term>
|
|
|
|
|
|
2020-01-16 17:51:19 +00:00
|
|
|
<listitem><para>Takes the root filesystem mount options to use. <varname>rootflags=</varname> is
|
|
|
|
|
honored by the initrd.</para>
|
|
|
|
|
|
|
|
|
|
<para>Note that unlike most kernel command line options this setting does not override settings made
|
|
|
|
|
in configuration files (specifically: the mount option string in
|
|
|
|
|
<filename>/etc/fstab</filename>). See
|
2023-08-22 16:52:36 +00:00
|
|
|
<citerefentry><refentrytitle>systemd-remount-fs.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>mount.usr=</varname></term>
|
|
|
|
|
|
2020-10-05 16:08:21 +00:00
|
|
|
<listitem><para>Takes the <filename>/usr/</filename> filesystem
|
2015-02-04 02:14:13 +00:00
|
|
|
to be mounted by the initrd. If
|
|
|
|
|
<varname>mount.usrfstype=</varname> or
|
|
|
|
|
<varname>mount.usrflags=</varname> is set, then
|
|
|
|
|
<varname>mount.usr=</varname> will default to the value set in
|
|
|
|
|
<varname>root=</varname>.</para>
|
|
|
|
|
|
2014-08-03 05:11:12 +00:00
|
|
|
<para>Otherwise, this parameter defaults to the
|
2020-10-05 16:08:21 +00:00
|
|
|
<filename>/usr/</filename> entry found in
|
2015-02-04 02:14:13 +00:00
|
|
|
<filename>/etc/fstab</filename> on the root filesystem.</para>
|
|
|
|
|
|
|
|
|
|
<para><varname>mount.usr=</varname> is honored by the initrd.
|
2023-08-22 16:52:36 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>mount.usrfstype=</varname></term>
|
|
|
|
|
|
2020-10-05 16:08:21 +00:00
|
|
|
<listitem><para>Takes the <filename>/usr/</filename> filesystem
|
2015-02-04 02:14:13 +00:00
|
|
|
type that will be passed to the mount command. If
|
|
|
|
|
<varname>mount.usr=</varname> or
|
|
|
|
|
<varname>mount.usrflags=</varname> is set, then
|
|
|
|
|
<varname>mount.usrfstype=</varname> will default to the value
|
|
|
|
|
set in <varname>rootfstype=</varname>.</para>
|
|
|
|
|
|
2014-08-03 05:11:12 +00:00
|
|
|
<para>Otherwise, this value will be read from the
|
2020-10-05 16:08:21 +00:00
|
|
|
<filename>/usr/</filename> entry in
|
2015-02-04 02:14:13 +00:00
|
|
|
<filename>/etc/fstab</filename> on the root filesystem.</para>
|
|
|
|
|
|
|
|
|
|
<para><varname>mount.usrfstype=</varname> is honored by the
|
2023-08-22 16:52:36 +00:00
|
|
|
initrd.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>mount.usrflags=</varname></term>
|
|
|
|
|
|
2020-10-05 16:08:21 +00:00
|
|
|
<listitem><para>Takes the <filename>/usr/</filename> filesystem
|
2015-02-04 02:14:13 +00:00
|
|
|
mount options to use. If <varname>mount.usr=</varname> or
|
|
|
|
|
<varname>mount.usrfstype=</varname> is set, then
|
2015-05-11 11:49:29 +00:00
|
|
|
<varname>mount.usrflags=</varname> will default to the value
|
2015-02-04 02:14:13 +00:00
|
|
|
set in <varname>rootflags=</varname>.</para>
|
|
|
|
|
|
2014-08-03 05:11:12 +00:00
|
|
|
<para>Otherwise, this value will be read from the
|
2020-10-05 16:08:21 +00:00
|
|
|
<filename>/usr/</filename> entry in
|
2015-02-04 02:14:13 +00:00
|
|
|
<filename>/etc/fstab</filename> on the root filesystem.</para>
|
|
|
|
|
|
|
|
|
|
<para><varname>mount.usrflags=</varname> is honored by the
|
2023-08-22 16:52:36 +00:00
|
|
|
initrd.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v217"/></listitem>
|
2015-02-04 02:14:13 +00:00
|
|
|
</varlistentry>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2022-05-02 14:42:50 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>roothash=</varname></term>
|
|
|
|
|
<term><varname>usrhash=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>These options are primarily read by
|
|
|
|
|
<citerefentry><refentrytitle>systemd-veritysetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>. When
|
|
|
|
|
set this indicates that the root file system (or <filename>/usr/</filename>) shall be mounted from
|
|
|
|
|
Verity volumes with the specified hashes. If these kernel command line options are set the root (or
|
|
|
|
|
<filename>/usr/</filename>) file system is thus mounted from a device mapper volume
|
2023-08-22 16:52:36 +00:00
|
|
|
<filename>/dev/mapper/root</filename> (or <filename>/dev/mapper/usr</filename>).</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
|
2022-05-02 14:42:50 +00:00
|
|
|
</varlistentry>
|
|
|
|
|
|
2016-12-13 11:45:19 +00:00
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.volatile=</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the
|
|
|
|
|
special value <option>state</option>.</para>
|
|
|
|
|
|
|
|
|
|
<para>If false (the default), this generator makes no changes to the mount tree and the system is booted up in
|
|
|
|
|
normal mode.</para>
|
|
|
|
|
|
|
|
|
|
<para>If true the generator ensures
|
|
|
|
|
<citerefentry><refentrytitle>systemd-volatile-root.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
man: "the initial RAM disk" → "the initrd"
In many places we spelled out the phrase behind "initrd" in full, but this
isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this
is just confusing to the reader. Let's just say "initrd" everywhere, people
understand what this refers to, and that it's in fact an initramfs image.
Also, s/i.e./e.g./ where appropriate.
Also, don't say "in RAM", when in fact it's virtual memory, whose pages
may or may not be loaded in page frames in RAM, and we have no control over
this.
Also, add <filename></filename> and other minor cleanups.
2022-09-15 12:43:59 +00:00
|
|
|
is run in the 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 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 unpopulated) volatile memory file system.</para>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2018-12-21 23:51:13 +00:00
|
|
|
<para>If set to <option>state</option> the generator will leave the root directory mount point unaltered,
|
2020-10-05 16:08:21 +00:00
|
|
|
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
|
2018-12-21 23:51:13 +00:00
|
|
|
lost at shutdown.</para>
|
|
|
|
|
|
|
|
|
|
<para>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.</para>
|
2016-12-13 11:45:19 +00:00
|
|
|
|
2020-10-05 16:08:21 +00:00
|
|
|
<para>Note that in none of these modes the root directory, <filename>/etc/</filename>, <filename>/var/</filename>
|
2016-12-13 11:45:19 +00:00
|
|
|
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>
|
|
|
|
|
|
2021-03-02 17:57:04 +00:00
|
|
|
<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 <literal>systemd.volatile=yes</literal>.</para>
|
|
|
|
|
|
|
|
|
|
<para>Also see <varname>root=tmpfs</varname> above, for a method to combine a
|
|
|
|
|
<literal>tmpfs</literal> file system with a regular <filename>/usr/</filename> file system (as
|
|
|
|
|
configured via <varname>mount.usr=</varname>). The main distinction between
|
|
|
|
|
<varname>systemd.volatile=yes</varname>, and <varname>root=tmpfs</varname> in combination
|
|
|
|
|
<varname>mount.usr=</varname> is that the former operates on top of a regular root file system and
|
|
|
|
|
temporarily obstructs the files and directories above its <filename>/usr/</filename> subdirectory,
|
|
|
|
|
while the latter does not hide any files, but simply mounts a unpopulated tmpfs as root file system
|
2023-08-22 16:52:36 +00:00
|
|
|
and combines it with a user picked <filename>/usr/</filename> file system.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
|
2016-12-13 11:45:19 +00:00
|
|
|
</varlistentry>
|
2019-12-21 06:17:59 +00:00
|
|
|
|
|
|
|
|
<varlistentry>
|
2023-05-25 06:44:21 +00:00
|
|
|
<term><varname>systemd.swap=</varname></term>
|
2019-12-21 06:17:59 +00:00
|
|
|
|
|
|
|
|
<listitem><para>Takes a boolean argument or enables the option if specified
|
|
|
|
|
without an argument. If disabled, causes the generator to ignore
|
|
|
|
|
any swap devices configured in <filename>/etc/fstab</filename>.
|
2023-08-22 16:52:36 +00:00
|
|
|
Defaults to enabled.</para>
|
|
|
|
|
|
2023-09-18 15:03:38 +00:00
|
|
|
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
|
2019-12-21 06:17:59 +00:00
|
|
|
</varlistentry>
|
2023-05-08 10:49:33 +00:00
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.mount-extra=<replaceable>WHAT</replaceable>:<replaceable>WHERE</replaceable>[:<replaceable>FSTYPE</replaceable>[:<replaceable>OPTIONS</replaceable>]]</varname></term>
|
2023-07-25 19:17:27 +00:00
|
|
|
<term><varname>rd.systemd.mount-extra=<replaceable>WHAT</replaceable>:<replaceable>WHERE</replaceable>[:<replaceable>FSTYPE</replaceable>[:<replaceable>OPTIONS</replaceable>]]</varname></term>
|
2023-05-08 10:49:33 +00:00
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Specifies the mount unit. Takes at least two and at most four fields separated with a colon
|
|
|
|
|
(<literal>:</literal>). Each field is handled as the corresponding fstab field. This option can be
|
2023-07-25 19:17:27 +00:00
|
|
|
specified multiple times. <varname>rd.systemd.mount-extra=</varname> is honored only in the initrd,
|
|
|
|
|
while <varname>systemd.mount-extra=</varname> is honored by both the main system and the initrd.
|
|
|
|
|
In the initrd, the mount point (and also source path if the mount is bind mount) specified in
|
|
|
|
|
<varname>systemd.mount-extra=</varname> is prefixed with <filename>/sysroot/</filename>.</para>
|
2023-05-08 10:49:33 +00:00
|
|
|
<para>Example:
|
|
|
|
|
<programlisting>
|
|
|
|
|
systemd.mount-extra=/dev/sda1:/mount-point:ext4:rw,noatime</programlisting>
|
|
|
|
|
</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v254"/>
|
2023-05-08 10:49:33 +00:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>systemd.swap-extra=<replaceable>WHAT</replaceable>[:<replaceable>OPTIONS</replaceable>]</varname></term>
|
2023-07-25 19:17:27 +00:00
|
|
|
<term><varname>rd.systemd.swap-extra=<replaceable>WHAT</replaceable>[:<replaceable>OPTIONS</replaceable>]</varname></term>
|
2023-05-08 10:49:33 +00:00
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
|
<para>Specifies the swap unit. Takes the block device to be used as a swap device, and optionally
|
2023-07-25 19:17:27 +00:00
|
|
|
takes mount options followed by a colon (<literal>:</literal>). This option can be specified
|
|
|
|
|
multiple times. <varname>rd.systemd.swap-extra=</varname> is honored only in the initrd, while
|
|
|
|
|
<varname>systemd.swap-extra=</varname> is honored by both the main system and the initrd.</para>
|
2023-05-08 10:49:33 +00:00
|
|
|
<para>Example:
|
|
|
|
|
<programlisting>
|
2023-10-10 13:45:20 +00:00
|
|
|
systemd.swap-extra=/dev/sda2:x-systemd.makefs</programlisting>
|
2023-05-08 10:49:33 +00:00
|
|
|
</para>
|
2023-08-22 16:52:36 +00:00
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v254"/>
|
2023-05-08 10:49:33 +00:00
|
|
|
</listitem>
|
|
|
|
|
</varlistentry>
|
2015-02-04 02:14:13 +00:00
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
2023-06-23 19:51:12 +00:00
|
|
|
<refsect1>
|
|
|
|
|
<title>System Credentials</title>
|
|
|
|
|
|
|
|
|
|
<variablelist class='system-credentials'>
|
|
|
|
|
<varlistentry>
|
|
|
|
|
<term><varname>fstab.extra</varname></term>
|
|
|
|
|
|
|
|
|
|
<listitem><para>This credential may contain addition mounts to establish, in the same format as
|
|
|
|
|
<citerefentry
|
|
|
|
|
project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>, with
|
2023-08-22 16:52:36 +00:00
|
|
|
one mount per line. It is read in addition to <filename>/etc/fstab</filename>.</para>
|
|
|
|
|
|
|
|
|
|
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
|
2023-06-23 19:51:12 +00:00
|
|
|
</varlistentry>
|
|
|
|
|
</variablelist>
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
2015-02-04 02:14:13 +00:00
|
|
|
<refsect1>
|
|
|
|
|
<title>See Also</title>
|
2023-12-22 18:09:32 +00:00
|
|
|
<para><simplelist type="inline">
|
|
|
|
|
<member><citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
|
|
|
|
|
<member><citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
|
|
|
|
|
<member><ulink url="https://systemd.io/ENVIRONMENT/">Known Environment Variables</ulink></member>
|
|
|
|
|
</simplelist></para>
|
2015-02-04 02:14:13 +00:00
|
|
|
</refsect1>
|
2012-06-27 13:27:29 +00:00
|
|
|
</refentry>
|