shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00
Code

man: systemd-nspawn(1): Fix some typos

Browse Source
This commit is contained in:
David Joaquín Shourabi Porcel 2024-04-12 22:14:47 +02:00
parent ac42b151f8
commit f4e3c6e5b3
No known key found for this signature in database
GPG Key ID: 60919F22552B95B9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man/systemd-nspawn.xml
View File

@ -369,7 +369,7 @@
<varlistentry>
<term><option>--read-only</option></term>
<listitem><para>Mount the container's root file system (and any other file systems container in the container
<listitem><para>Mount the container's root file system (and any other file systems contained in the container
image) read-only. This has no effect on additional mounts made with <option>--bind=</option>,
<option>--tmpfs=</option> and similar options. This mode is implied if the container image file or directory is
marked read-only itself. It is also implied if <option>--volatile=</option> is used. In this case the container
@ -404,7 +404,7 @@
<filename>/efi/</filename> or <filename>/boot/</filename> are prohibited in case such a partition
exists in the container image operated on, and even if <option>--volatile=state</option> is used the
hypothetical file <filename index="false">/etc/foobar</filename> is potentially writable if
<option>--bind=/etc/foobar</option> if used to mount it from outside the read-only container
<option>--bind=/etc/foobar</option> is used to mount it from outside the read-only container
<filename>/etc/</filename> directory.</para>
<para>The <option>--ephemeral</option> option is closely related to this setting, and provides similar