Documentation/userspace-api/unshare.rst

10 ----------
14 --------
17 	3) Cost
21 	7) Low Level Design
26 -----------
37 outside the confinement of all-or-nothing shared resources of legacy
45 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
53 -----------
59 even non-threaded applications if they have a need to disassociate
60 from default shared namespace. The following lists two use-cases
63 2.1 Per-security context namespaces
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
68 such as per-user and/or per-security context instance of /tmp, /var/tmp or
69 per-security context instance of a user's home directory, isolate user
74 of shared-tree feature in the Linux kernel, even regular Linux systems
92 3) Cost
93 -------
99 There is a cost associated with altering existing, well tested and
103 the benefits of this new feature can exceed its cost.
106 ---------------
123 ---------------------------
126 	unshare - disassociate parts of the process execution context
145 	The flags argument specifies one or bitwise-or'ed of several of
166 	On success, zero returned. On failure, -1 is returned and errno is
169 	EPERM	CLONE_NEWNS was specified by a non-root process (process
178 	The unshare() call is Linux-specific and  should  not be used
185 --------------------
194   1) clone operates on a newly allocated not-yet-active task
231 7) Low Level Design
232 -------------------
284 and CLONE_THREAD, return -EINVAL since they are not implemented yet.
297 ---------------------
303      yet, return -EINVAL.
323 --------------