diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-09-15 13:43:59 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-09-20 16:48:50 +0200 |
| commit | b66a6e1a5838b874b789820c090dd6850cf10513 (patch) | |
| tree | df30d43665c3bd1e29d6efe294c2c9e5e237dfd0 /man/systemd-fstab-generator.xml | |
| parent | 483bf5643aa1bdb498d7055ea20f534eac1d1486 (diff) | |
| download | systemd-b66a6e1a5838b874b789820c090dd6850cf10513.tar.gz | |
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.
Diffstat (limited to 'man/systemd-fstab-generator.xml')
| -rw-r--r-- | man/systemd-fstab-generator.xml | 23 |
1 files changed, 10 insertions, 13 deletions
diff --git a/man/systemd-fstab-generator.xml b/man/systemd-fstab-generator.xml index 21c3ea94a7..b7908377a4 100644 --- a/man/systemd-fstab-generator.xml +++ b/man/systemd-fstab-generator.xml @@ -70,13 +70,10 @@ <term><varname>fstab=</varname></term> <term><varname>rd.fstab=</varname></term> - <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 by the initial RAM disk (initrd) while - <varname>fstab=</varname> is honored by both the main system - and the initrd.</para></listitem> + <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 + <varname>fstab=</varname> is honored by both the main system and the initrd.</para></listitem> </varlistentry> <varlistentry> @@ -194,12 +191,12 @@ <para>If true the generator ensures <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 - 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> + 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> <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 |