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 | |
| 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')
| -rw-r--r-- | man2/clone.2 | 13 | ||||
| -rw-r--r-- | man2/mount.2 | 23 | ||||
| -rw-r--r-- | man2/unshare.2 | 7 |
3 files changed, 24 insertions, 19 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) diff --git a/man2/mount.2 b/man2/mount.2 index 6915c3ac5c..96566df701 100644 --- a/man2/mount.2 +++ b/man2/mount.2 @@ -37,7 +37,7 @@ .\" 2008-10-06, mtk: move umount*() material into separate umount.2 page. .\" 2008-10-06, mtk: Add discussion of namespaces. .\" -.TH MOUNT 2 2008-10-06 "Linux" "Linux Programmer's Manual" +.TH MOUNT 2 2008-11-19 "Linux" "Linux Programmer's Manual" .SH NAME mount \- mount file system .SH SYNOPSIS @@ -376,9 +376,12 @@ Since Linux 2.4 the set-user-ID and set-group-ID bits are just silently ignored in this case. .\" The change is in patch-2.4.0-prerelease. .SS Per-process Namespaces -Starting with kernel 2.4.19, Linux provides per-process namespaces. -A namespace is the set of file system mounts that are visible to a process. -Namespaces can be (and usually are) shared between multiple processes, +Starting with kernel 2.4.19, Linux provides +per-process mount-point namespaces. +A mount-point namespace is the set of file system mounts that +are visible to a process. +Mount-point namespaces can be (and usually are) +shared between multiple processes, and changes to the namespace (i.e., mounts and unmounts) by one process are visible to all other processes sharing the same namespace. (The pre-2.4.19 Linux situation can be considered as one in which there @@ -386,11 +389,11 @@ was a single namespace was shared by every process on the system.) A child process created by .BR fork (2) -shares its parent's namespace; -the namespace is preserved across an +shares its parent's mount-point namespace; +the mount-point namespace is preserved across an .BR execve (2). -A process can obtain a private namespace if: +A process can obtain a private mount-point namespace if: it was created using the .BR clone () .BR CLONE_NEWNS @@ -404,7 +407,7 @@ or it calls with the .BR CLONE_NEWNS flag, -which causes the caller's namespace to obtain a private copy +which causes the caller's mount-point namespace to obtain a private copy of the namespace that it was previously sharing with other processes, so that future mounts and unmounts by the caller are invisible to other processes (except child processes that the caller @@ -412,8 +415,8 @@ subsequently creates) and vice versa. The Linux-specific .I /proc/PID/self -file exposes the list of mount points in the namespace of the process with -the specified ID; see +file exposes the list of mount points in the mount-point +namespace of the process with the specified ID; see .BR proc (5) for details. .SH "SEE ALSO" diff --git a/man2/unshare.2 b/man2/unshare.2 index ed3bd5d90f..0895f01db4 100644 --- a/man2/unshare.2 +++ b/man2/unshare.2 @@ -18,7 +18,7 @@ .\" FIXME Document CLONE_NEWUTS, which is new in 2.6.19 .\" FIXME Document CLONE_SYSVSEM, which is new in 2.6.26 .\" -.TH UNSHARE 2 2007-07-26 "Linux" "Linux Programmer's Manual" +.TH UNSHARE 2 2008-11-19 "Linux" "Linux Programmer's Manual" .SH NAME unshare \- disassociate parts of the process execution context .SH SYNOPSIS @@ -34,7 +34,7 @@ unshare \- disassociate parts of the process execution context .BR unshare () allows a process to disassociate parts of its execution context that are currently being shared with other processes. -Part of the execution context, such as the namespace, is shared +Part of the execution context, such as the mount-point namespace, is shared implicitly when a new process is created using .BR fork (2) or @@ -87,7 +87,8 @@ effect as the .BR clone (2) .B CLONE_NEWNS flag. -Unshare the namespace, so that the calling process has a private copy of +Unshare the mount-point namespace, +so that the calling process has a private copy of its namespace which is not shared with any other process. Specifying this flag automatically implies .B CLONE_FS |