|
73 | 73 | since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and |
74 | 74 | the host and domain name.</para> |
75 | 75 |
|
76 | | - <para>Like <citerefentry |
77 | | - project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> the |
78 | | - <command>systemd-nspawn</command> command may be invoked on any directory tree containing an operating system tree, |
| 76 | + <para><command>systemd-nspawn</command> may be invoked on any directory tree containing an operating system tree, |
79 | 77 | using the <option>--directory=</option> command line option. By using the <option>--machine=</option> option an OS |
80 | | - tree is automatically searched in a couple of locations, most importantly in |
| 78 | + tree is automatically searched for in a couple of locations, most importantly in |
81 | 79 | <filename>/var/lib/machines</filename>, the suggested directory to place container images installed on the |
82 | 80 | system.</para> |
83 | 81 |
|
|
935 | 933 | <literal>tmpfs</literal> instance, and |
936 | 934 | <filename>/usr</filename> from the OS tree is mounted into it |
937 | 935 | in read-only mode (the system thus starts up with read-only OS |
938 | | - resources, but pristine state and configuration, any changes |
939 | | - to the either are lost on shutdown). When the mode parameter |
| 936 | + image, but pristine state and configuration, any changes |
| 937 | + are lost on shutdown). When the mode parameter |
940 | 938 | is specified as <option>state</option>, the OS tree is |
941 | 939 | mounted read-only, but <filename>/var</filename> is mounted as |
942 | 940 | a <literal>tmpfs</literal> instance into it (the system thus |
|
0 commit comments