mkdir - create a directory
int mkdir(const char *pathname, mode_t mode);
mkdir(2) attempts to create a directory named pathname.
mode specifies the permissions to use. It is modified by the process's umask(2) in the usual way: the permissions of the created file are (mode .
The newly created directory will be owned by the effective uid of the process. If the directory containing the file has the set group id bit set, or if the filesystem is mounted with BSD group semantics, the new directory will inherit the group ownership from its parent; otherwise it will be owned by the effective gid of the process.
If the parent directory has the set group id bit set then so will the newly created directory.
mkdir(2) returns zero on success, or -1 if an error occurred (in which case, errno is set appropriately).
- The filesystem containing pathname does not support the creation of directories.
- pathname already exists (not necessarily as a directory). This includes the case where pathname is a symbolic link, dangling or not.
- pathname points outside your accessible address space.
- The parent directory does not allow write permission to the process, or one of the directories in pathname did not allow search (execute) permission.
- pathname was too long.
- A directory component in pathname does not exist or is a dangling symbolic link.
- A component used as a directory in pathname is not, in fact, a directory.
- Insufficient kernel memory was available.
- pathname refers to a file on a read-only filesystem.
- Too many symbolic links were encountered in resolving pathname.
- The device containing pathname has no room for the new directory.
- The new directory cannot be created because the user's disk quota is exhausted.
SVr4, POSIX, BSD, SYSV, X/OPEN. SVr4 documents additional EIO, EMULTIHOP and ENOLINK error conditions; POSIX.1 omits ELOOP.
There are many infelicities in the protocol underlying NFS. Some of these affect mkdir(2).
mkdir(1), chmod(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2)