X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=aea50559f04f643e87ad6173390bc749f3a75663;hb=e2d7c1a0758ce80d7cb439745deefefdffd67655;hp=cb0605bcd10d67e6cfeef909d8058d27d137a883;hpb=108e8cd11e88bd4795a62bf335921d438592601c;p=elogind.git diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index cb0605bcd..aea50559f 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -70,7 +70,7 @@ systemd-nspawn may be used to run a command or OS in a light-weight namespace container. In many ways it is similar to - chroot1, + chroot1, but more powerful since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and the host and domain @@ -98,15 +98,15 @@ involved with boot and systems management. In contrast to - chroot1 systemd-nspawn + chroot1 systemd-nspawn may be used to boot full Linux-based operating systems in a container. Use a tool like - yum8, - debootstrap8, + yum8, + debootstrap8, or - pacman8 + pacman8 to set up an OS directory tree suitable as file system hierarchy for systemd-nspawn containers. @@ -393,7 +393,7 @@ additional capabilities to grant the container. Takes a comma-separated list of capability names, see - capabilities7 + capabilities7 for more information. Note that the following capabilities will be granted in any way: CAP_CHOWN, @@ -581,7 +581,7 @@ accessible via machinectl1 and shown by tools such as - ps1. If + ps1. If the container does not run an init system, it is recommended to set this option to no. Note @@ -770,10 +770,10 @@ See Also systemd1, - chroot1, - yum8, - debootstrap8, - pacman8, + chroot1, + yum8, + debootstrap8, + pacman8, systemd.slice5, machinectl1