create a directory NAME mkdir, mkdirat - create a directory LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include...create a directory NAME mkdir, mkdirat - create a directory LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include...Seccomp user-space notification mechanism NAME seccomp_unotify - Seccomp user-space notification mechanism LIBRARY Standard C library ( libc , -lc ) SYNOPSIS #include <linux/seccom…...ask are used), and returns the previous value of the mask. The umask is used by open (2), mkdir (2), and other system calls that create files to modify the permissions placed on…...er Linux, mknod () cannot be used to create directories. One should make directories with mkdir (2). STANDARDS POSIX.1-2008. HISTORY mknod () SVr4, 4.4BSD, POSIX.1-2001 (but see…...er Linux, mknod () cannot be used to create directories. One should make directories with mkdir (2). STANDARDS POSIX.1-2008. HISTORY mknod () SVr4, 4.4BSD, POSIX.1-2001 (but see…...and placing a copy of the (statically linked) busybox (1) executable in that directory. $ mkdir /tmp/rootfs $ ls -id /tmp/rootfs # Show inode number of new root directory 319459…...directories which are still being used. SEE ALSO rm (1), rmdir (1), chdir (2), chmod (2), mkdir (2), rename (2), unlink (2), unlinkat (2)...e rooted at ' / '. In particular, the superuser can escape from a "chroot jail" by doing: mkdir foo; chroot foo; cd .. This call does not close open file descriptors, and such f…...n fcntl (2); take a new file's group from parent directory, as described in chown (2) and mkdir (2)) S_ISVTX (01000) sticky bit (restricted deletion flag, as described in unlink…...n fcntl (2); take a new file's group from parent directory, as described in chown (2) and mkdir (2)) S_ISVTX (01000) sticky bit (restricted deletion flag, as described in unlink…...n fcntl (2); take a new file's group from parent directory, as described in chown (2) and mkdir (2)) S_ISVTX (01000) sticky bit (restricted deletion flag, as described in unlink…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…....4. NOTES Ownership of new files When a new file is created (by, for example, open (2) or mkdir (2)), its owner is made the same as the filesystem user ID of the creating proces…...3.17 memfd_create (2) 3.17 memfd_secret (2) 5.14 migrate_pages (2) 2.6.16 mincore (2) 2.4 mkdir (2) 1.0 mkdirat (2) 2.6.16 mknod (2) 1.0 mknodat (2) 2.6.16 mlock (2) 2.0 mlock2 …