attempts to create a directory named
specifies the permissions to use.
It is modified by the process's
in the usual way: the permissions of the created directory are
(mode & ~umask & 0777).
Other mode bits of the created directory depend on the operating system.
For Linux, see below.
The newly created directory will be owned by the effective user ID of the
If the directory containing the file has the set-group-ID
bit set, or if the file system is mounted with BSD group semantics
(mount -o bsdgroups
mount -o grpid),
the new directory will inherit the group ownership from its parent;
otherwise it will be owned by the effective group ID of the process.
If the parent directory has the set-group-ID bit set then so will the
newly created directory.
returns zero on success, or -1 if an error occurred (in which case,
is set appropriately).
The parent directory does not allow write permission to the process,
or one of the directories in
did not allow search permission.
already exists (not necessarily as a directory).
This includes the case where
is a symbolic link, dangling or not.
pathname points outside your accessible address space.
Too many symbolic links were encountered in resolving
The number of links to the parent directory would exceed
pathname was too long.
A directory component in
does not exist or is a dangling symbolic link.
Insufficient kernel memory was available.
The device containing
has no room for the new directory.
The new directory cannot be created because the user's disk quota is
A component used as a directory in
is not, in fact, a directory.
The file system containing
does not support the creation of directories.
refers to a file on a read-only file system.
SVr4, BSD, POSIX.1-2001.
Under Linux apart from the permission bits, only the
mode bit is honored.
That is, under Linux the created directory actually gets mode
(mode & ~umask & 01777).
There are many infelicities in the protocol underlying NFS.
Some of these affect