diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2008-11-19 14:23:47 -0500 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2008-11-25 20:54:07 -0500 |
| commit | 4df2eb09d1718c5979a640a398e49ce2041f67df (patch) | |
| tree | 9e162eef71e0888d8ab7dac8c7845f0852c6c5d3 /man2/clone.2 | |
| parent | 667417b33c102e4b0e39d544fe131eabd54c6442 (diff) | |
| download | man-pages-4df2eb09d1718c5979a640a398e49ce2041f67df.tar.gz | |
clone.2, mount.2, unshare.2, proc.5, path_resolution.7: Global fix: s/namespace/mount-point namespace/, as appropriate
In recent times, a number of other namespace flags have been
added to clone(2). As such, it is no longer clear to use
the generic term "namespace" to refer to the particular
namespace controlled by CLONE_NEWNS; instead, use the
term "mount-point namespace".
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man2/clone.2')
| -rw-r--r-- | man2/clone.2 | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/man2/clone.2 b/man2/clone.2 index cdae8ecf02..3fa947e382 100644 --- a/man2/clone.2 +++ b/man2/clone.2 @@ -255,9 +255,9 @@ This flag can't be specified in conjunction with .BR CLONE_SYSVSEM . .TP .BR CLONE_NEWNS " (since Linux 2.4.19)" -Start the child in a new namespace. +Start the child in a new mount-point namespace. -Every process lives in a namespace. +Every process lives in a mount-point namespace. The .I namespace of a process is the data (the set of mounts) describing the file hierarchy @@ -268,20 +268,21 @@ or .BR clone () where the .B CLONE_NEWNS -flag is not set, the child lives in the same namespace as the parent. +flag is not set, the child lives in the same mount-point +namespace as the parent. The system calls .BR mount (2) and .BR umount (2) -change the namespace of the calling process, and hence affect +change the mount-point namespace of the calling process, and hence affect all processes that live in the same namespace, but do not affect -processes in a different namespace. +processes in a different mount-point namespace. After a .BR clone () where the .B CLONE_NEWNS -flag is set, the cloned child is started in a new namespace, +flag is set, the cloned child is started in a new mount-point namespace, initialized with a copy of the namespace of the parent. Only a privileged process (one having the \fBCAP_SYS_ADMIN\fP capability) |