X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-nspawn.xml;h=03c39fc3def88631ff30b51abe06ac1d4293e554;hp=70ebf94e0ff4ff5fc65c45921a57a9d2d63f579b;hb=7aaa27f2196a96411006fb8afa5718ed0ea88544;hpb=8f7a3c1402a8de36b2c63935358a53510d2fe7c1 diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 70ebf94e0..03c39fc3d 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -61,7 +61,7 @@ container. In many ways it is similar to chroot1, but more powerful since it fully virtualizes the file - system hierachy, as well as the process tree, the + system hierarchy, as well as the process tree, the various IPC subsystems and the host and domain name. @@ -99,14 +99,14 @@ Note that systemd-nspawn will mount file systems private to the container to /dev, - /dev/.run and similar. These will + /run and similar. These will not be visible outside of the container, and their contents will be lost when the container exits. Note that running two systemd-nspawn containers from the same directory tree will not make processes in them - see each other. The PID namespace seperation of the + see each other. The PID namespace separation of the two containers is complete and the containers will share very few runtime objects except for the underlying file system. @@ -139,6 +139,19 @@ used. + + + + + Run the command + under specified user, create home + directory and cd into it. As rest + of systemd-nspawn, this is not + the security feature and limits + against accidental changes only. + + +