Differences between current version and previous revision of mkdir(2).
Other diffs: Previous Major 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 2 | Last edited on Monday, March 10, 2003 2:54:46 pm | by PerryLorier | Revert |
@@ -32,9 +32,9 @@
;[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]
.
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)
