man: owned to → owned by

[thirdparty/systemd.git] / man / systemd-nspawn.xml

diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index f1d6f14812519b6765078d71fcdb17853e4f85c1..db3f10c3a2aa92ddf686049f47a3f66e35085ea3 100644 (file)
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -368,12 +368,16 @@
         <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
         details.</para>
 
-        <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work correctly
-        with operating systems in the container that can boot up with only <filename>/usr</filename> mounted, and are
-        able to automatically populate <filename>/var</filename>, and also <filename>/etc</filename> in case of
-        <literal>--volatile=yes</literal>. The <option>overlay</option> option does not require any particular
-        preparations in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file
-        systems in a number of ways, and hence compatibility is limited.</para></listitem>
+        <para>Note that setting this option to <option>yes</option> or <option>state</option> will only work
+        correctly with operating systems in the container that can boot up with only
+        <filename>/usr/</filename> mounted, and are able to automatically populate <filename>/var/</filename>
+        (and <filename>/etc/</filename> in case of <literal>--volatile=yes</literal>). Specifically, this
+        means that operating systems that follow the historic split of <filename>/bin/</filename> and
+        <filename>/lib/</filename> (and related directories) from <filename>/usr/</filename> (i.e. where the
+        former are not symlinks into the latter) are not supported by <literal>--volatile=yes</literal> as
+        container payload. The <option>overlay</option> option does not require any particular preparations
+        in the OS, but do note that <literal>overlayfs</literal> behaviour differs from regular file systems
+        in a number of ways, and hence compatibility is limited.</para></listitem>
       </varlistentry>
 
       <varlistentry>
@@ -709,10 +713,10 @@
       <varlistentry>
         <term><option>--private-users-chown</option></term>
 
-        <listitem><para>If specified, all files and directories in the container's directory tree will adjusted so that
-        they are owned to the appropriate UIDs/GIDs selected for the container (see above). This operation is
-        potentially expensive, as it involves descending and iterating through the full directory tree of the
-        container. Besides actual file ownership, file ACLs are adjusted as well.</para>
+        <listitem><para>If specified, all files and directories in the container's directory tree will be
+        adjusted so that they are owned by the appropriate UIDs/GIDs selected for the container (see above).
+        This operation is potentially expensive, as it involves iterating through the full directory tree of
+        the container. Besides actual file ownership, file ACLs are adjusted as well.</para>
 
         <para>This option is implied if <option>--private-users=pick</option> is used. This option has no effect if
         user namespacing is not used.</para></listitem>
@@ -1390,7 +1394,7 @@
       <title>Boot a minimal
       <ulink url="https://www.archlinux.org">Arch Linux</ulink> distribution in a container</title>
 
-      <programlisting># pacstrap -c -d ~/arch-tree/ base
+      <programlisting># pacstrap -c ~/arch-tree/ base
 # systemd-nspawn -bD ~/arch-tree/</programlisting>
 
       <para>This installs a minimal Arch Linux distribution into the