change root directory NAME chroot - change root directory LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include <unis......orking directory. The current working directory is left unchanged by execve (2). SEE ALSO chroot (2), getcwd (3), path_resolution (7)...orking directory. The current working directory is left unchanged by execve (2). SEE ALSO chroot (2), getcwd (3), path_resolution (7)...new_root . EINVAL The current root directory is not a mount point (because of an earlier chroot (2)). EINVAL The current root is on the rootfs (initial ramfs) mount; see NOTES. …...filesystem attributes, so that the calling process no longer shares its root directory ( chroot (2)), current directory ( chdir (2)), or umask ( umask (2)) attributes with any o…...ted relative to dirfd . The effect of this flag is as though the calling process had used chroot (2) to (temporarily) modify its root directory (to the directory referred to by …...the use of pathnames or file descriptors. Thus, getrandom () can be useful in cases where chroot (2) makes /dev pathnames invisible, and where an application (e.g., a daemon dur…...rectory of the current process (e.g., because the process set a new filesystem root using chroot (2) without changing its current directory into the new root). Such behavior can…...unt namespaces Changing the mount namespace requires that the caller possess both CAP_SYS_CHROOT and CAP_SYS_ADMIN capabilities in its own user namespace and CAP_SYS_ADMIN in th…...thin the single directory hierarchy. Bind mounts may cross filesystem boundaries and span chroot (2) jails. The filesystemtype and data arguments are ignored. The remaining bits…...des the root of the filesystem, the current working directory, and the umask. Any call to chroot (2), chdir (2), or umask (2) performed by the calling process or the child proce…...des the root of the filesystem, the current working directory, and the umask. Any call to chroot (2), chdir (2), or umask (2) performed by the calling process or the child proce…...des the root of the filesystem, the current working directory, and the umask. Any call to chroot (2), chdir (2), or umask (2) performed by the calling process or the child proce…...dir (2) 1.0 chmod (2) 1.0 chown (2) 2.2 See chown (2) for version details chown32 (2) 2.4 chroot (2) 1.0 clock_adjtime (2) 2.6.39 clock_getres (2) 2.6 clock_gettime (2) 2.6 cloc…