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 2017-09-15 "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 _POSIX_C_SOURCE\ >=\ 200809L
48 attempts to create a directory named
53 specifies the mode for the new directory (see
55 It is modified by the process's
57 in the usual way: in the absence of a default ACL, the mode of the
59 .RI ( mode " & ~" umask " & 0777)."
62 bits are honored for the created directory depends on the operating system.
63 For Linux, see NOTES below.
65 The newly created directory will be owned by the effective user ID of the
67 If the directory containing the file has the set-group-ID
68 bit set, or if the filesystem is mounted with BSD group semantics
69 .RI ( "mount -o bsdgroups"
71 .IR "mount -o grpid" ),
72 the new directory will inherit the group ownership from its parent;
73 otherwise it will be owned by the effective group ID of the process.
75 If the parent directory has the set-group-ID bit set, then so will the
76 newly created directory.
82 system call operates in exactly the same way as
84 except for the differences described here.
86 If the pathname given in
88 is relative, then it is interpreted relative to the directory
89 referred to by the file descriptor
91 (rather than relative to the current working directory of
92 the calling process, as is done by
94 for a relative pathname).
104 is interpreted relative to the current working
105 directory of the calling process (like
116 for an explanation of the need for
122 return zero on success, or \-1 if an error occurred (in which case,
124 is set appropriately).
128 The parent directory does not allow write permission to the process,
129 or one of the directories in
131 did not allow search permission.
133 .BR path_resolution (7).)
136 The user's quota of disk blocks or inodes on the filesystem has been
141 already exists (not necessarily as a directory).
142 This includes the case where
144 is a symbolic link, dangling or not.
147 .IR pathname " points outside your accessible address space."
150 The final component ("basename") of the new directory's
153 (e.g., it contains characters not permitted by the underlying filesystem).
156 Too many symbolic links were encountered in resolving
160 The number of links to the parent directory would exceed
164 .IR pathname " was too long."
167 A directory component in
169 does not exist or is a dangling symbolic link.
172 Insufficient kernel memory was available.
175 The device containing
177 has no room for the new directory.
180 The new directory cannot be created because the user's disk quota is
184 A component used as a directory in
186 is not, in fact, a directory.
189 The filesystem containing
191 does not support the creation of directories.
195 refers to a file on a read-only filesystem.
197 The following additional errors can occur for
202 is not a valid file descriptor.
208 is a file descriptor referring to a file other than a directory.
211 was added to Linux in kernel 2.6.16;
212 library support was added to glibc in version 2.4.
215 SVr4, BSD, POSIX.1-2001, POSIX.1-2008.
216 .\" SVr4 documents additional EIO, EMULTIHOP
221 Under Linux, apart from the permission bits, the
226 There are many infelicities in the protocol underlying NFS.
230 On older kernels where
232 is unavailable, the glibc wrapper function falls back to the use of
236 is a relative pathname,
237 glibc constructs a pathname based on the symbolic link in
239 that corresponds to the
253 .BR path_resolution (7)