1 .\" This manpage is Copyright (C) 1992 Drew Eckhardt;
2 .\" and Copyright (C) 1993 Michael Haardt
3 .\" and Copyright (C) 1993,1994 Ian Jackson
4 .\" and Copyright (C) 2006, 2014 Michael Kerrisk
6 .\" %%%LICENSE_START(GPL_NOVERSION_ONELINE)
7 .\" You may distribute it under the terms of the GNU General
8 .\" Public License. It comes with NO WARRANTY.
11 .TH MKDIR 2 2014-08-19 "Linux" "Linux Programmer's Manual"
13 mkdir, mkdirat \- create a directory
16 .B #include <sys/stat.h>
17 .B #include <sys/types.h>
18 .\" .B #include <unistd.h>
20 .BI "int mkdir(const char *" pathname ", mode_t " mode );
22 .BR "#include <fcntl.h> " "/* Definition of AT_* constants */"
23 .B #include <sys/stat.h>
25 .BI "int mkdirat(int " dirfd ", const char *" pathname ", mode_t " mode );
29 Feature Test Macro Requirements for glibc (see
30 .BR feature_test_macros (7)):
39 _XOPEN_SOURCE\ >=\ 700 || _POSIX_C_SOURCE\ >=\ 200809L
49 attempts to create a directory named
54 specifies the permissions to use.
55 It is modified by the process's
57 in the usual way: in the absence of a default acl, the permissions of the
59 .RI ( mode " & ~" umask " & 0777)."
60 Other mode bits of the created directory depend on the operating system.
63 The newly created directory will be owned by the effective user ID of the
65 If the directory containing the file has the set-group-ID
66 bit set, or if the filesystem is mounted with BSD group semantics
67 .RI ( "mount -o bsdgroups"
69 .IR "mount -o grpid" ),
70 the new directory will inherit the group ownership from its parent;
71 otherwise it will be owned by the effective group ID of the process.
73 If the parent directory has the set-group-ID bit set, then so will the
74 newly created directory.
80 system call operates in exactly the same way as
82 except for the differences described here.
84 If the pathname given in
86 is relative, then it is interpreted relative to the directory
87 referred to by the file descriptor
89 (rather than relative to the current working directory of
90 the calling process, as is done by
92 for a relative pathname).
102 is interpreted relative to the current working
103 directory of the calling process (like
114 for an explanation of the need for
120 return zero on success, or \-1 if an error occurred (in which case,
122 is set appropriately).
126 The parent directory does not allow write permission to the process,
127 or one of the directories in
129 did not allow search permission.
131 .BR path_resolution (7).)
134 The user's quota of disk blocks or inodes on the filesystem has been
139 already exists (not necessarily as a directory).
140 This includes the case where
142 is a symbolic link, dangling or not.
145 .IR pathname " points outside your accessible address space."
148 Too many symbolic links were encountered in resolving
152 The number of links to the parent directory would exceed
156 .IR pathname " was too long."
159 A directory component in
161 does not exist or is a dangling symbolic link.
164 Insufficient kernel memory was available.
167 The device containing
169 has no room for the new directory.
172 The new directory cannot be created because the user's disk quota is
176 A component used as a directory in
178 is not, in fact, a directory.
181 The filesystem containing
183 does not support the creation of directories.
187 refers to a file on a read-only filesystem.
189 The following additional errors can occur for
194 is not a valid file descriptor.
200 is a file descriptor referring to a file other than a directory.
203 was added to Linux in kernel 2.6.16;
204 library support was added to glibc in version 2.4.
207 SVr4, BSD, POSIX.1-2001, POSIX.1-2008.
208 .\" SVr4 documents additional EIO, EMULTIHOP
213 Under Linux, apart from the permission bits, only the
219 There are many infelicities in the protocol underlying NFS.
223 On older kernels where
225 is unavailable, the glibc wrapper function falls back to the use of
229 is a relative pathname,
230 glibc constructs a pathname based on the symbolic link in
232 that corresponds to the
245 .BR path_resolution (7)