.\" Modified 2003-04-23 by Michael Kerrisk
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
.\"
-.TH MKNOD 2 2008-12-01 "Linux" "Linux Programmer's Manual"
+.TH MKNOD 2 2010-09-20 "Linux" "Linux Programmer's Manual"
.SH NAME
mknod \- create a special or ordinary file
.SH SYNOPSIS
.in
.sp
.BR mknod ():
-_BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE\ >=\ 500
+.ad l
+.RS 4
+_BSD_SOURCE || _SVID_SOURCE || _XOPEN_SOURCE\ >=\ 500 ||
+_XOPEN_SOURCE\ &&\ _XOPEN_SOURCE_EXTENDED
+.RE
+.ad
.SH DESCRIPTION
The system call
.BR mknod ()
.B S_IFSOCK
.\" (S_IFSOCK since Linux 1.2.4)
to specify a regular file (which will be created empty), character
-special file, block special file, FIFO (named pipe), or Unix domain socket,
+special file, block special file, FIFO (named pipe), or UNIX domain socket,
respectively.
(Zero file type is equivalent to type
.BR S_IFREG .)
.B EPERM
.I mode
requested creation of something other than a regular file,
-FIFO (named pipe), or Unix domain socket, and the caller
+FIFO (named pipe), or UNIX domain socket, and the caller
is not privileged (Linux: does not have the
.B CAP_MKNOD
capability);
-.\" For Unix domain sockets and regular files, EPERM is only returned in
+.\" For UNIX domain sockets and regular files, EPERM is only returned in
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
.\" use mknod() to make these files.
also returned if the file system containing
Under Linux, this call cannot be used to create directories.
One should make directories with
.BR mkdir (2).
-.\" and one should make Unix domain sockets with socket(2) and bind(2).
+.\" and one should make UNIX domain sockets with socket(2) and bind(2).
There are many infelicities in the protocol underlying NFS.
Some of these affect