Differences between current version and predecessor to the previous major change of mkdir(2).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Monday, March 10, 2003 2:55:36 pm | by PerryLorier | |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:23:42 am | by perry | Revert |
@@ -1,151 +1,40 @@
-MKDIR
-!!!MKDIR
-NAME
-SYNOPSIS
-DESCRIPTION
-RETURN VALUE
-ERRORS
-CONFORMING TO
-SEE ALSO
-----
!!NAME
+mkdir - create a directory
-
-mkdir - create a directory
!!SYNOPSIS
-
-
-__#include
-__''pathname''__, mode_t__ ''mode''__);
-
+ __#include <sys/stat.h>__
+ __#include <sys/types.h>__
+ __int mkdir(const char *
__''pathname''__, mode_t__ ''mode''__);__
!!DESCRIPTION
+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 __.
-__mkdir__ attempts to create a directory named
-''pathname''.
+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.
-''mode'' specifies
the permissions to use. It is modified
-by
the process's __umask__ in the usual way: the
-permissions of
the created file are __(mode
-__
.
+If
the parent directory has
the set group id bit set then so will
the newly
created directory
.
-
-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.
!!RETURN VALUE
+mkdir(2) returns zero on success, or -1 if an error occurred (in which case, ''errno'' is set appropriately).
-
-__mkdir__ returns zero on success, or -1 if an error
-occurred (in which case, ''errno'' is set
-appropriately).
!!ERRORS
+;[EPERM]: The filesystem containing ''pathname'' does not support the creation of directories.
+;[EEXIST]: ''pathname'' already exists (not necessarily as a directory). This includes the case where ''pathname'' is a symbolic link, dangling or not.
+;[EFAULT]: ''pathname'' points outside your accessible address space.
+;[EACCES]: The parent directory does not allow write permission to the process, or one of the directories in ''pathname'' did not allow search (execute) permission.
+;[ENAMETOOLONG]: ''pathname'' was too long.
+;[ENOENT]: A directory component in ''pathname'' does not exist or is a dangling symbolic link.
+;[ENOTDIR]: A component used as a directory in ''pathname'' is not, in fact, a directory.
+;[ENOMEM]: Insufficient kernel memory was available.
+;[EROFS]: ''pathname'' refers to a file on a read-only filesystem.
+;[ELOOP]: Too many symbolic links were encountered in resolving ''pathname''.
+;[ENOSPC]: The device containing ''pathname'' has no room for the new directory.
+;[ENOSPC]: The new directory cannot be created because the user's disk quota is exhausted.
-
-__EPERM__
-
-
-The filesystem containing ''pathname'' does not support
-the creation of directories.
-
-
-__EEXIST__
-
-
-''pathname'' already exists (not necessarily as a
-directory). This includes the case where ''pathname'' is
-a symbolic link, dangling or not.
-
-
-__EFAULT__
-
-
-''pathname'' points outside your accessible address
-space.
-
-
-__EACCES__
-
-
-The parent directory does not allow write permission to the
-process, or one of the directories in ''pathname'' did
-not allow search (execute) permission.
-
-
-__ENAMETOOLONG__
-
-
-''pathname'' was too long.
-
-
-__ENOENT__
-
-
-A directory component in ''pathname'' does not exist or
-is a dangling symbolic link.
-
-
-__ENOTDIR__
-
-
-A component used as a directory in ''pathname'' is not,
-in fact, a directory.
-
-
-__ENOMEM__
-
-
-Insufficient kernel memory was available.
-
-
-__EROFS__
-
-
-''pathname'' refers to a file on a read-only
-filesystem.
-
-
-__ELOOP__
-
-
-Too many symbolic links were encountered in resolving
-''pathname''.
-
-
-__ENOSPC__
-
-
-The device containing ''pathname'' has no room for the
-new directory.
-
-
-__ENOSPC__
-
-
-The new directory cannot be created because the user's disk
-quota is exhausted.
!!CONFORMING TO
+SVr4, POSIX, BSD, SYSV, X/OPEN. SVr4 documents additional [EIO], [EMULTIHOP] and [ENOLINK] error conditions; POSIX.1 omits [ELOOP].
-
-SVr4, POSIX, BSD, SYSV, X/OPEN. SVr4 documents additional
-EIO, EMULTIHOP and ENOLINK error conditions; POSIX.1 omits
-ELOOP.
-
-
-
-__
mkdir__
.
+There are many infelicities in the protocol underlying [
NFS]
. Some of these affect mkdir(2)
.
!!SEE ALSO
-
-
-
-
-
-----
+mkdir(1), chmod(2), mknod(2), mount(2), rmdir(2), stat(2), umask(2), unlink(2)
