clone.2: Remove wording that suggests CLONE_NEW* flags are for containers

These flags are used for implementing many other interesting
things by now.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-11-08 21:52:37 +01:00
parent f5d5180f5c
commit 1270276bc3
1 changed files with 0 additions and 5 deletions

View File

@ -438,7 +438,6 @@ Create the process in a new cgroup namespace.
If this flag is not set, then (as with
.BR fork (2))
the process is created in the same cgroup namespaces as the calling process.
This flag is intended for the implementation of containers.
.IP
For further information on cgroup namespaces, see
.BR cgroup_namespaces (7).
@ -457,7 +456,6 @@ If this flag is not set, then (as with
.BR fork (2)),
the process is created in the same IPC namespace as
the calling process.
This flag is intended for the implementation of containers.
.IP
An IPC namespace provides an isolated view of System\ V IPC objects (see
.BR sysvipc (7))
@ -500,7 +498,6 @@ If this flag is not set, then (as with
.BR fork (2))
the process is created in the same network namespace as
the calling process.
This flag is intended for the implementation of containers.
.IP
A network namespace provides an isolated view of the networking stack
(network device interfaces, IPv4 and IPv6 protocol stacks,
@ -571,7 +568,6 @@ If this flag is not set, then (as with
.BR fork (2))
the process is created in the same PID namespace as
the calling process.
This flag is intended for the implementation of containers.
.IP
For further information on PID namespaces, see
.BR namespaces (7)
@ -644,7 +640,6 @@ If this flag is not set, then (as with
.BR fork (2))
the process is created in the same UTS namespace as
the calling process.
This flag is intended for the implementation of containers.
.IP
A UTS namespace is the set of identifiers returned by
.BR uname (2);