...es in other UTS namespaces. When a process creates a new UTS namespace using clone (2) or unshare (2) with the CLONE_NEWUTS flag, the hostname and domain name of the new UTS nam….../proc/ pid /cgroup file. When a process creates a new cgroup namespace using clone (2) or unshare (2) with the CLONE_NEWCGROUP flag, its current cgroups directories become the c…...e (2) with the CLONE_NEWPID flag, or the first child created by a process after a call to unshare (2) using the CLONE_NEWPID flag) has the PID 1, and is the "init" process for t…...ied via a file descriptor that refers to one of the /proc/ pid /ns files described below. unshare (2) The unshare (2) system call moves the calling process to a new namespace. I…...(2), and /proc/uptime . Currently, the only way to create a time namespace is by calling unshare (2) with the CLONE_NEWTIME flag. This call creates a new time namespace but does…...the same view in these files.) A new mount namespace is created using either clone (2) or unshare (2) with the CLONE_NEWNS flag. When a new mount namespace is created, its mount…...requires a kernel that is configured with the CONFIG_IPC_NS option. SEE ALSO nsenter (1), unshare (1), clone (2), setns (2), unshare (2), mq_overview (7), namespaces (7), sysvip…...espace is the user namespace of the process that creates the user namespace via a call to unshare (2) or clone (2) with the CLONE_NEWUSER flag. The kernel imposes (since Linux 3…...requires a kernel that is configured with the CONFIG_NET_NS option. SEE ALSO nsenter (1), unshare (1), clone (2), veth (4), proc (5), sysfs (5), namespaces (7), user_namespaces …...open (2), pipe (2)); • employ CLONE_* flags that create new namespaces with clone (2) and unshare (2) (but, since Linux 3.8, creating user namespaces does not require any capabi…