Updated CONFORMING TO section

man2/_exit.2

@@ -62,7 +62,7 @@ is equivalent to
 .SH "RETURN VALUE"
 These functions do not return.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD.
+SVr4, POSIX.1-2001, 4.3BSD.
 The function \fB_Exit\fP() was introduced by C99.
 .SH NOTES
 For a discussion on the effects of an exit, the transmission of

man2/accept.2

@@ -250,9 +250,10 @@ SVr4, 4.4BSD
 first appeared in 4.2BSD).
 The BSD man page documents five possible error returns
 (EBADF, ENOTSOCK, EOPNOTSUPP, EWOULDBLOCK, EFAULT).
-SUSv3 documents errors EAGAIN, EBADF, ECONNABORTED, EINTR, EINVAL, EMFILE,
+POSIX.1-2001 documents errors 
-ENFILE, ENOBUFS, ENOMEM, ENOTSOCK, EOPNOTSUPP, EPROTO, EWOULDBLOCK. In
+EAGAIN, EBADF, ECONNABORTED, EINTR, EINVAL, EMFILE,
-addition, SUSv2 documents EFAULT and ENOSR.
+ENFILE, ENOBUFS, ENOMEM, ENOTSOCK, EOPNOTSUPP, EPROTO, EWOULDBLOCK. 
+In addition, SUSv2 documents EFAULT and ENOSR.
 .LP
 On Linux, the new socket returned by
 .BR accept () 
@@ -272,7 +273,7 @@ the socket returned from
 The third argument of
 .BR accept ()
 was originally declared as an `int *' (and is that under libc4 and libc5
-and on many other systems like 4.x BSD, SunOS 4, SGI); a POSIX 1003.1g draft
+and on many other systems like 4.x BSD, SunOS 4, SGI); a POSIX.1g draft
 standard wanted to change it into a `size_t *', and that is what it is
 for SunOS 5.
 Later POSIX drafts have `socklen_t *', and so do the Single Unix Specification

man2/access.2

@@ -171,7 +171,7 @@ doing so using
 creates a security hole, because the user might exploit the short time
 interval between checking and opening the file to manipulate it.
 .SH "CONFORMING TO"
-SVID, AT&T, POSIX, X/OPEN, 4.3BSD
+SVr4, POSIX.1-2001, 4.3BSD
 .SH "SEE ALSO"
 .BR chmod (2),
 .BR chown (2),

man2/acct.2

@@ -115,11 +115,12 @@ refers to a file on a read-only file system.
 .B EUSERS
 There are no more free file structures or we ran out of memory.
 .SH "CONFORMING TO"
-SVr4 (but not POSIX).  SVr4 documents an EBUSY error condition,
+SVr4 (but not POSIX).  
-but no EISDIR or ENOSYS. Also AIX and HPUX document EBUSY (attempt is made
+.\" SVr4 documents an EBUSY error condition, but no EISDIR or ENOSYS. 
-to enable accounting when it is already enabled), as does Solaris
+.\" Also AIX and HP-UX document EBUSY (attempt is made
-(attempt is made to enable accounting using the same file that is
+.\" to enable accounting when it is already enabled), as does Solaris
-currently being used).
+.\" (attempt is made to enable accounting using the same file that is
+.\" currently being used).
 .SH NOTES
 No accounting is produced for programs running when a crash occurs.  In
 particular, nonterminating processes are never accounted for.

man2/alarm.2

@@ -77,7 +77,7 @@ is a bad idea.
 Scheduling delays can, as ever, cause the execution of the process to
 be delayed by an arbitrary amount of time.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD
+SVr4, POSIX.1-2001, 4.3BSD
 .SH "SEE ALSO"
 .BR gettimeofday (2),
 .BR pause (2),

man2/arch_prctl.2

@@ -117,9 +117,10 @@ is not a valid subcommand.
 is outside the process address space.
 .SH AUTHOR
 Man page written by Andi Kleen.
-.SH CONFORMANCE
+.SH "CONFORMING TO"
 .BR arch_prctl ()
-is a Linux/x86-64 extension and should not be used in programs intended to be portable.
+is a Linux/x86-64 extension and should not be used in programs intended 
+to be portable.
 .SH "SEE ALSO"
 .BR mmap (2),
 .BR modify_ldt (2),

man2/brk.2

@@ -65,7 +65,7 @@ and
 is set to
 .BR ENOMEM .
 .SH "CONFORMING TO"
-4.3BSD
+4.3BSD; SUSv1, marked LEGACY in SUSv2, removed in POSIX.1-2001.
 
 .BR brk ()
 and 
@@ -82,7 +82,6 @@ Common are \fIint\fP, \fIssize_t\fP, \fIptrdiff_t\fP, \fIintptr_t\fP.
 .\" \fIptrdiff_t\fP (libc4, libc5, ulibc, glibc2.0, 2.1),
 .\" \fIintptr_t\fP (e.g. XPGv5, AIX, SunOS 5.8, 5.9, FreeBSD 4.7, NetBSD 1.6,
 .\" Tru64 5.1, glibc2.2).
-XPGv6 obsoletes this function.
 .SH "SEE ALSO"
 .BR execve (2),
 .BR getrlimit (2),

man2/chdir.2

@@ -116,19 +116,7 @@ is only available if
 .B _BSD_SOURCE
 is defined.
 .SH "CONFORMING TO"
-The 
+SVr4, 4.4BSD, POSIX.1-2001.
-.BR chdir ()
-call is compatible with SVr4, SVID, POSIX, X/OPEN, 4.4BSD.  
-SVr4 documents
-additional EINTR, ENOLINK, and EMULTIHOP error conditions but has
-no ENOMEM.  POSIX.1 does not have ENOMEM or ELOOP error conditions.
-X/OPEN does not have EFAULT, ENOMEM or EIO error conditions.
-
-The
-.BR fchdir ()
-call is compatible with SVr4, 4.4BSD and X/OPEN.
-SVr4 documents additional EIO, EINTR, and ENOLINK error conditions.
-X/OPEN documents additional EINTR and EIO error conditions.
 .SH "SEE ALSO"
 .BR chroot (2),
 .BR path_resolution (2),

man2/chmod.2

@@ -185,25 +185,7 @@ See above.
 .B EROFS
 See above.
 .SH "CONFORMING TO"
-The
+4.4BSD, SVr4, POSIX.1-2001.
-.BR chmod ()
-call conforms to SVr4, SVID, POSIX, X/OPEN, 4.4BSD.
-SVr4 documents EINTR, ENOLINK and EMULTIHOP returns, but no
-ENOMEM.  POSIX.1 does not document EFAULT, ENOMEM, or EIO error
-conditions.
-.PP
-The 
-.BR fchmod ()
-call conforms to 4.4BSD and SVr4.
-SVr4 documents additional EINTR and ENOLINK error conditions.
-POSIX requires the
-.BR fchmod ()
-function if at least one of
-.B _POSIX_MAPPED_FILES
-and
-.B _POSIX_SHARED_MEMORY_OBJECTS
-is defined, and documents additional ENOSYS and EINVAL error
-conditions, but does not document EIO.
 .SH "SEE ALSO"
 .BR chown (2),
 .BR execve (2),

man2/chown.2

@@ -158,17 +158,16 @@ is only available if
 .B _BSD_SOURCE
 is defined.
 .SH "CONFORMING TO"
-The
+4.4BSD, SVr4, POSIX.1-2001.
-.BR chown ()
+
-call conforms to SVr4, SVID, POSIX, X/OPEN.  The 4.4BSD version can only be
+The 4.4BSD version can only be
 used by the superuser (that is, ordinary users cannot give away files).
-SVr4 documents EINVAL, EINTR, ENOLINK and EMULTIHOP returns, but no
+.\" chown():
-ENOMEM.  POSIX.1 does not document ENOMEM or ELOOP error conditions.
+.\" SVr4 documents EINVAL, EINTR, ENOLINK and EMULTIHOP returns, but no
-.PP
+.\" ENOMEM.  POSIX.1 does not document ENOMEM or ELOOP error conditions.
-The 
+.\" fchown():
-.BR fchown ()
+.\" SVr4 documents additional EINVAL, EIO, EINTR, and ENOLINK 
-call conforms to 4.4BSD and SVr4.
+.\" error conditions.
-SVr4 documents additional EINVAL, EIO, EINTR, and ENOLINK error conditions.
 .SH RESTRICTIONS
 The \fBchown\fP() semantics are deliberately violated on NFS file systems
 which have UID mapping enabled.  Additionally, the semantics of all system

man2/chroot.2

@@ -103,10 +103,10 @@ is not a directory.
 .B EPERM
 The caller has insufficient privilege.
 .SH "CONFORMING TO"
-SVr4, SVID, 4.4BSD, X/OPEN.  This function is not part of POSIX.1.
+SVr4, 4.4BSD, SUSv2 (marked LEGACY).  
-SVr4 documents additional EINTR, ENOLINK and EMULTIHOP error conditions.
+This function is not part of POSIX.1-2001.
-X/OPEN does not document EIO, ENOMEM or EFAULT error conditions.
+.\" SVr4 documents additional EINTR, ENOLINK and EMULTIHOP error conditions.
-This interface is marked as legacy by X/OPEN.
+.\" X/OPEN does not document EIO, ENOMEM or EFAULT error conditions.
 .SH NOTES
 A child process created via
 .BR fork (2)

man2/close.2

@@ -79,10 +79,12 @@ call was interrupted by a signal.
 .B EIO
 An I/O error occurred.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  SVr4 documents an additional
+SVr4, 4.3BSD, POSIX.1-2001.  
-ENOLINK error condition.
+.\" SVr4 documents an additional ENOLINK error condition.
 .SH NOTES
-Not checking the return value of close is a common but nevertheless
+Not checking the return value of 
+.BR close ()
+is a common but nevertheless
 serious programming error.  It is quite possible that errors on a
 previous
 .BR write (2)

man2/dup.2

@@ -124,9 +124,10 @@ without closing
 .I newfd
 first.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD. SVr4 documents additional
+SVr4, 4.3BSD, POSIX.1-2001. 
-EINTR and ENOLINK error conditions.  POSIX.1 adds EINTR.
+.\" SVr4 documents additional
-The EBUSY return is Linux-specific.
+.\" EINTR and ENOLINK error conditions.  POSIX.1 adds EINTR.
+.\" The EBUSY return is Linux-specific.
 .SH "SEE ALSO"
 .BR close (2),
 .BR fcntl (2),

man2/execve.2

@@ -185,11 +185,13 @@ file has an SUID or SGID bit set.
 .B ETXTBSY
 Executable was open for writing by one or more processes.
 .SH "CONFORMING TO"
-SVr4, SVID, X/OPEN, 4.3BSD.  POSIX does not document the #!  behavior
+SVr4, 4.3BSD, POSIX.1-2001.  
-but is otherwise compatible.  SVr4 documents additional error
+POSIX.1 does not document the #!  behavior
-conditions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not
+but is otherwise compatible.  
-document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL,
+.\" SVr4 documents additional error
-EISDIR or ELIBBAD error conditions.
+.\" conditions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not
+.\" document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL,
+.\" EISDIR or ELIBBAD error conditions.
 .SH NOTES
 SUID and SGID processes can not be \fBptrace\fP()d.
 

man2/fcntl.2

@@ -150,7 +150,7 @@ On Linux this command can only change the
 and 
 .BR O_NONBLOCK 
 flags.
-.\" FIXME According to SUSv3, O_SYNC should also be modifiable
+.\" FIXME According to POSIX.1-2001, O_SYNC should also be modifiable
 .\" via fcntl(2), but currently Linux does not permit this
 .\" See http://bugzilla.kernel.org/show_bug.cgi?id=5994
 .P
@@ -877,7 +877,7 @@ placed by
 and
 .BR fcntl (2).
 
-POSIX 1003.1-2001 allows
+POSIX.1-2001 allows
 .I l_len
 to be negative. (And if it is, the interval described by the lock
 covers bytes
@@ -930,19 +930,16 @@ has permission to send signals to.
 Despite this error return, the file descriptor owner is set,
 and signals will be sent to the owner.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  Only the operations F_DUPFD,
+SVr4, 4.3BSD, POSIX.1-2001.  
+Only the operations F_DUPFD,
 F_GETFD, F_SETFD, F_GETFL, F_SETFL, F_GETLK, F_SETLK, F_SETLKW, 
 F_GETOWN, and F_SETOWN are specified in POSIX.1.
+
 F_GETSIG, F_SETSIG, F_NOTIFY, F_GETLEASE, and F_SETLEASE
 are Linux specific.
 (Define the _GNU_SOURCE macro to obtain these definitions.)
-The flags legal for F_GETFL/F_SETFL are those supported by
+.\" .PP
-.BR open (2)
+.\" SVr4 documents additional EIO, ENOLINK and EOVERFLOW error conditions.
-and vary between these systems; O_APPEND, O_NONBLOCK, O_RDONLY,
-and O_RDWR are specified in POSIX.1.  SVr4 supports several other
-options and flags not documented here.
-.PP
-SVr4 documents additional EIO, ENOLINK and EOVERFLOW error conditions.
 .SH "SEE ALSO"
 .BR dup2 (2),
 .BR flock (2),

man2/fdatasync.2

@@ -82,11 +82,11 @@ is available,
 .B _POSIX_SYNCHRONIZED_IO
 is defined in <unistd.h> to a value greater than 0. (See also
 .BR sysconf (3).)
-.\" POSIX 1003.1-2001: It shall be defined to -1 or 0 or 200112L.
+.\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
 .\" -1: unavailable, 0: ask using sysconf().
 .\" glibc defines them to 1.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1b
 .SH "SEE ALSO"
 .BR fsync (2)
 .BR sync_file_range (2),

man2/fork.2

@@ -79,9 +79,7 @@ capability.
 .BR fork ()
 failed to allocate the necessary kernel structures because memory is tight.
 .SH "CONFORMING TO"
-The
+SVr4, 4.3BSD, POSIX.1-2001.
-.BR fork ()
-call conforms to SVr4, SVID, POSIX, X/OPEN, 4.3BSD.
 .SH EXAMPLE
 See
 .BR pipe (2)

man2/getcontext.2

@@ -116,7 +116,7 @@ Do not leave the handler using \fIlongjmp\fP(): it is undefined
 what would happen with contexts. Use \fIsiglongjmp\fP() or
 \fIsetcontext\fP() instead.
 .SH "CONFORMING TO"
-SUSv2
+SUSv2, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR sigaction (2),
 .BR sigaltstack (2),

man2/getdents.2

@@ -113,7 +113,8 @@ No such directory.
 .B ENOTDIR
 File descriptor does not refer to a directory.
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents additional ENOLINK, EIO error conditions.
+SVr4.
+.\" SVr4 documents additional ENOLINK, EIO error conditions.
 .SH "SEE ALSO"
 .BR readdir (2),
 .BR readdir (3)

man2/getdomainname.2

@@ -77,6 +77,7 @@ the caller is unprivileged (Linux: does not have the
 capability).
 .SH "CONFORMING TO"
 POSIX does not specify these calls.
+.\" But they appear on most systems...
 .SH "SEE ALSO"
 .BR gethostname (2),
 .BR sethostname (2),

man2/getgid.2

@@ -42,7 +42,7 @@ returns the effective group ID of the current process.
 .SH ERRORS
 These functions are always successful.
 .SH "CONFORMING TO"
-POSIX, 4.3BSD
+POSIX.1-2001, 4.3BSD
 .SH "SEE ALSO"
 .BR setgid (2),
 .BR setregid (2)

man2/getgroups.2

@@ -116,12 +116,13 @@ is only available if
 .B _BSD_SOURCE
 is defined.
 .SH "CONFORMING TO"
-SVr4, SVID (issue 4 only; these calls were not present in SVr3),
+SVr4, 4.3BSD.
-X/OPEN, 4.3BSD.  The
+The
 .BR getgroups ()
-function is in POSIX.1.  Since
+function is in POSIX.1-2001.
+Since
 .BR setgroups ()
-requires privilege, it is not covered by POSIX.1.
+requires privilege, it is not covered by POSIX.1-2001.
 .SH "SEE ALSO"
 .BR getgid (2),
 .BR setgid (2),

man2/gethostid.2

@@ -56,9 +56,12 @@ argument is stored in the file
 returns the 32-bit identifier for the current host as set by
 .BR sethostid (2).
 .SH "CONFORMING TO"
-4.2BSD.  These functions were dropped in 4.4BSD.
+4.2BSD; these functions were dropped in 4.4BSD.
-POSIX.1 does not define these functions, but ISO/IEC 9945-1:1990 mentions
+SVr4 includes 
-them in B.4.4.1.  SVr4 includes 
+.BR gethostid ()
+but not
+.BR sethostid ().
+POSIX.1-2001 specifies 
 .BR gethostid ()
 but not
 .BR sethostid ().

man2/gethostname.2

@@ -79,13 +79,13 @@ the caller did not have the
 capability.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD  (this interfaces first appeared in 4.2BSD).
-POSIX 1003.1-2001 specifies
+POSIX.1-2001 specifies
 .BR gethostname ()
 but not
 .BR sethostname ().
 .SH NOTES
 SUSv2 guarantees that `Host names are limited to 255 bytes'.
-POSIX 1003.1-2001 guarantees that `Host names (not including
+POSIX.1-2001 guarantees that `Host names (not including
 the terminating null byte) are limited to HOST_NAME_MAX bytes'.
 .SH "GLIBC NOTES"
 The GNU C library implements 

man2/getpagesize.2

@@ -61,9 +61,9 @@ This call first appeared in 4.2BSD.
 SVr4, 4.4BSD, SUSv2.
 In SUSv2 the
 .BR getpagesize ()
-call is labeled "legacy", and in POSIX 1003.1-2001
+call is labeled LEGACY, and in POSIX.1-2001
 it has been dropped.
-HPUX does not have this call.
+HP-UX does not have this call.
 .SH NOTES
 Whether
 .BR getpagesize ()

man2/getpeername.2

@@ -90,12 +90,16 @@ is a file, not a socket.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (the
 .BR getpeername ()
-function call first appeared in 4.2BSD).
+function call first appeared in 4.2BSD), POSIX.1-2001.
 .SH NOTE
 The third argument of 
 .BR getpeername ()
-is in reality an `int *' (and this is what 4.x BSD and libc4 and libc5 have).
+is in reality an 
-Some POSIX confusion resulted in the present socklen_t, also used by glibc.
+.I int *
+(and this is what 4.x BSD and libc4 and libc5 have).
+Some POSIX confusion resulted in the present 
+.IR socklen_t , 
+also used by glibc.
 See also
 .BR accept (2).
 .SH "SEE ALSO"

man2/getpid.2

@@ -39,7 +39,7 @@ routines that generate unique temporary filenames.)
 .BR getppid ()
 returns the process ID of the parent of the current process.
 .SH "CONFORMING TO"
-POSIX, 4.3BSD, SVID
+POSIX.1-2001, 4.3BSD, SVr4
 .SH "SEE ALSO"
 .BR fork (2),
 .BR kill (2),

man2/getpriority.2

@@ -158,7 +158,7 @@ The nice value is preserved across
 .BR execve (2). 
 
 The details on the condition for EPERM depend on the system.
-The above description is what SUSv3 says, and seems to be followed on
+The above description is what POSIX.1-2001 says, and seems to be followed on
 all System V-like systems.
 Linux kernels before 2.6.12 required the real or 
 effective user ID of the caller to match
@@ -200,7 +200,8 @@ structure with fields of type
 defined in
 .IR <sys/time.h> .)
 .SH "CONFORMING TO"
-SVr4, 4.4BSD (these function calls first appeared in 4.2BSD).
+SVr4, 4.4BSD (these function calls first appeared in 4.2BSD),
+POSIX.1-2001.
 .SH "SEE ALSO"
 .BR nice (1),
 .BR fork (2),

man2/getresuid.2

@@ -52,7 +52,9 @@ is set appropriately.
 One of the arguments specified an address outside the calling program's
 address space.
 .SH "CONFORMING TO"
-This call is Linux-specific.
+These calls are non-standard; 
+they also appear on HP-UX and some of the BSDs.
+
 The prototype is given by glibc since version 2.3.2
 provided _GNU_SOURCE is defined.
 .SH "SEE ALSO"

man2/getrlimit.2

@@ -401,7 +401,7 @@ inherits its parents resource limits.
 Resource limits are preserved across
 .BR execve (2).
 .SH "CONFORMING TO"
-SVr4, 4.3BSD.
+SVr4, 4.3BSD, POSIX.1-2001.
 .BR RLIMIT_MEMLOCK
 and 
 .BR RLIMIT_NPROC

man2/getrusage.2

@@ -88,7 +88,13 @@ points outside the accessible address space.
 .I who
 is invalid.
 .SH "CONFORMING TO"
-SVr4, 4.3BSD
+SVr4, 4.3BSD. 
+POSIX.1-2001 specifies 
+.BR getrusage (),
+but only specifies the fields
+.I ru_utime
+and
+.IR ru_stime .
 .SH NOTES
 Including
 .I <sys/time.h>
@@ -105,7 +111,7 @@ is set to
 then the resource usages of child processes
 are automatically included in the value returned by
 .BR RUSAGE_CHILDREN ,
-although POSIX 1003.1-2001 explicitly prohibits this.
+although POSIX.1-2001 explicitly prohibits this.
 This non-conformance is rectified in Linux 2.6.9 and later.
 .\" See the description of getrusage() in XSH.
 .\" A similar statement was also in SUSv2.

man2/getsid.2

@@ -53,7 +53,7 @@ No process with process ID
 .I p
 was found.
 .SH "CONFORMING TO"
-SVr4, POSIX 1003.1-2001.
+SVr4, POSIX.1-2001.
 .SH NOTES
 Linux does not return EPERM.
 .LP

man2/getsockname.2

@@ -87,8 +87,9 @@ is a file, not a socket.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (the
 .BR getsockname ()
-function call appeared in 4.2BSD).  SVr4 documents additional ENOMEM
+function call appeared in 4.2BSD), POSIX.1-2001.
-and ENOSR error codes. 
+.\" SVr4 documents additional ENOMEM
+.\" and ENOSR error codes. 
 .SH NOTE
 The third argument of 
 .BR getsockname ()

man2/getsockopt.2

@@ -157,16 +157,23 @@ The argument
 .I s
 is a file, not a socket.
 .SH "CONFORMING TO"
-SVr4, 4.4BSD (these system calls first appeared in 4.2BSD).
+SVr4, 4.4BSD (these system calls first appeared in 4.2BSD), 
-SVr4 documents additional ENOMEM and ENOSR error codes, but does
+ POSIX.1-2001.
-not document the 
+.\" SVr4 documents additional ENOMEM and ENOSR error codes, but does
-.BR SO_SNDLOWAT ", " SO_RCVLOWAT ", " SO_SNDTIMEO ", " SO_RCVTIMEO
+.\" not document the 
-options
+.\" .BR SO_SNDLOWAT ", " SO_RCVLOWAT ", " SO_SNDTIMEO ", " SO_RCVTIMEO
+.\" options
 .SH NOTE
-The fifth argument of 
+The 
+.I optlen
+argument of 
 .BR getsockopt " and " setsockopt
-is in reality an int [*] (and this is what 4.x BSD and libc4 and libc5 have).
+is in reality an 
-Some POSIX confusion resulted in the present socklen_t, also used by glibc.
+.I "int [*]"
+(and this is what 4.x BSD and libc4 and libc5 have).
+Some POSIX confusion resulted in the present 
+.IR socklen_t , 
+also used by glibc.
 See also
 .BR accept (2).
 .SH BUGS

man2/gettimeofday.2

@@ -224,7 +224,8 @@ Traditionally, the fields of
 .I struct timeval 
 were longs.
 .SH "CONFORMING TO"
-SVr4, 4.3BSD. POSIX 1003.1-2001 describes
+SVr4, 4.3BSD. 
+POSIX.1-2001 describes
 .BR gettimeofday ()
 but not 
 .BR settimeofday ().

man2/getuid.2

@@ -43,7 +43,7 @@ returns the effective user ID of the current process.
 .SH ERRORS
 These functions are always successful.
 .SH "CONFORMING TO"
-POSIX, 4.3BSD.
+POSIX.1-2001, 4.3BSD.
 .SH HISTORY
 In Unix V6 the \fBgetuid\fP() call returned (euid << 8) + uid.
 Unix V7 introduced separate calls \fBgetuid\fP() and \fBgeteuid\fP().

man2/ioctl.2

@@ -116,15 +116,18 @@ Often the
 call has unwanted side effects, that can be avoided under Linux
 by giving it the O_NONBLOCK flag.
 .SH "CONFORMING TO"
-No single standard.  Arguments, returns, and semantics of
+No single standard.  
+Arguments, returns, and semantics of
 .BR ioctl (2) 
 vary according to the device driver in question (the call is used as a
 catch-all for operations that don't cleanly fit the Unix stream I/O
-model). See 
+model). 
+See 
 .BR ioctl_list (2)
 for a list of many of the known 
 .BR ioctl ()
-calls.  The
+calls.  
+The
 .BR ioctl ()
 function call appeared in Version 7 AT&T Unix.
 .SH "SEE ALSO"

man2/kill.2

@@ -109,13 +109,13 @@ has explicitly installed signal handlers.
 This is done to assure the
 system is not brought down accidentally.
 .LP
-POSIX 1003.1-2001 requires that \fIkill(\-1,sig)\fP send \fIsig\fP
+POSIX.1-2001 requires that \fIkill(\-1,sig)\fP send \fIsig\fP
 to all processes that the current process may send signals to,
 except possibly for some implementation-defined system processes.
 Linux allows a process to signal itself, but on Linux the call
 \fIkill(\-1,sig)\fP does not signal the current process.
 .LP
-POSIX 1003.1-2003 requires that if a process sends a signal to itself,
+POSIX.1-2001 requires that if a process sends a signal to itself,
 and the sending thread does not have the signal blocked, 
 and no other thread
 has it unblocked or is waiting for it in \fIsigwait\fP(), at least one
@@ -143,10 +143,10 @@ or the real user ID of the sender matched that of the receiver.
 From kernel 1.2.3 until 1.3.77, a signal could be sent if the
 effective user ID of the sender matched either the real or effective
 user ID of the receiver.
-The current rules, which conform to POSIX 1003.1-2001, were adopted
+The current rules, which conform to POSIX.1-2001, were adopted
 in kernel 1.3.78.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX.1, X/OPEN, 4.3BSD, POSIX 1003.1-2001
+SVr4, 4.3BSD, POSIX.1-2001
 .SH "SEE ALSO"
 .BR _exit (2),
 .BR killpg (2),

man2/killpg.2

@@ -105,7 +105,7 @@ for all target processes.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (The
 .BR killpg ()
-function call first appeared in 4.0BSD).
+function call first appeared in 4BSD), POSIX.1-2001.
 .SH "SEE ALSO"
 .BR getpgrp (2),
 .BR kill (2),

man2/link.2

@@ -152,9 +152,10 @@ Some other implementations behave in the same manner as Linux.
 .\" thread in the Austin mailing list reported that some
 .\" other (System V) implementations did/do the same -- MTK, Apr 05
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, 4.3BSD, X/OPEN.  SVr4 documents additional ENOLINK and
+SVr4, 4.3BSD, POSIX.1-2001 (except as noted above).
-EMULTIHOP error conditions; POSIX.1 does not document ELOOP.
+.\" SVr4 documents additional ENOLINK and
-X/OPEN does not document EFAULT, ENOMEM or EIO.
+.\" EMULTIHOP error conditions; POSIX.1 does not document ELOOP.
+.\" X/OPEN does not document EFAULT, ENOMEM or EIO.
 .SH BUGS
 On NFS file systems, the return code may be wrong in case the NFS server
 performs the link creation and dies before it can say so.  Use

man2/listen.2

@@ -110,7 +110,8 @@ The socket is not of a type that supports the
 .BR listen ()
 operation.
 .SH "CONFORMING TO"
-Single Unix, 4.4BSD, POSIX 1003.1g draft. The
+4.4BSD, POSIX.1-2001.
+The
 .BR listen ()
 function call first appeared in 4.2BSD. 
 .SH BUGS

man2/lseek.2

@@ -114,10 +114,11 @@ The resulting file offset cannot be represented in an
 .I fildes
 is associated with a pipe, socket, or FIFO.
 .SH "CONFORMING TO"
-SVr4, POSIX, 4.3BSD
+SVr4, 4.3BSD, POSIX.1-2001.
 .SH RESTRICTIONS
 Some devices are incapable of seeking and POSIX does not specify which
-devices must support it.
+devices must support 
+.BR lseek ().
 
 Linux specific restrictions: using \fBlseek\fP() on a tty device returns
 \fBESPIPE\fP.
@@ -143,7 +144,7 @@ L_INCR	SEEK_CUR
 L_XTND	SEEK_END
 .TE
 .PP
-SVR1-3 returns \fIlong\fP instead of \fIoff_t\fP, BSD returns \fIint\fP.
+SVr1-3 returns \fIlong\fP instead of \fIoff_t\fP, BSD returns \fIint\fP.
 .PP
 Note that file descriptors created by
 .BR dup (2)

man2/madvise.2

@@ -146,9 +146,9 @@ The
 .BR madvise ()
 function first appeared in 4.4BSD.
 .SH "CONFORMING TO"
-POSIX.1b (POSIX.4).
+POSIX.1b.
-POSIX 1003.1-2001 describes
+POSIX.1-2001 describes
-.B posix_madvise
+.BR posix_madvise ()
 with constants POSIX_MADV_NORMAL, etc.,
 with a behaviour close to that described here. There is a similar
 .BR posix_fadvise ()

man2/mkdir.2

@@ -103,8 +103,8 @@ does not support the creation of directories.
 .I pathname
 refers to a file on a read-only filesystem.
 .SH "CONFORMING TO"
-SVr4, POSIX, BSD, X/OPEN.  SVr4 documents additional EIO, EMULTIHOP
+SVr4, BSD, POSIX.1-2001.
-and ENOLINK error conditions; POSIX.1 omits ELOOP.
+.\" SVr4 documents additional EIO, EMULTIHOP
 .SH NOTES
 Under Linux apart from the permission bits, only the S_ISVTX mode bit
 is honored. That is, under Linux the created directory actually gets mode

man2/mknod.2

@@ -144,12 +144,12 @@ does not support the type of node requested.
 .I pathname
 refers to a file on a read-only filesystem.
 .SH "CONFORMING TO"
-SVr4 (but the call requires privilege and is thus not in POSIX),
+SVr4, 4.4BSD, POSIX.1-2001 (but see below).  
-4.4BSD.  The Linux version differs from the SVr4 version in that it
+.\" The Linux version differs from the SVr4 version in that it
-does not require root permission to create pipes, also in that no
+.\" does not require root permission to create pipes, also in that no
-EMULTIHOP, ENOLINK, or EINTR error is documented.
+.\" EMULTIHOP, ENOLINK, or EINTR error is documented.
 .SH NOTES
-POSIX 1003.1-2001 says: "The only portable use of
+POSIX.1-2001 says: "The only portable use of
 .BR mknod ()
 is to create a FIFO-special file. If
 .I mode

man2/mlock.2

@@ -171,7 +171,7 @@ and
 automatically round
 .I addr
 down to the nearest page boundary.
-However, POSIX 1003.1-2001 allows an implementation to require that
+However, POSIX.1-2001 allows an implementation to require that
 .I addr
 is page aligned, so portable applications should ensure this.
 .SS "Limits and permissions"
@@ -307,7 +307,7 @@ are available,
 .B _POSIX_MEMLOCK
 is defined in <unistd.h> to a value greater than 0. (See also
 .BR sysconf (3).)
-.\" POSIX 1003.1-2001: It shall be defined to -1 or 0 or 200112L.
+.\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
 .\" -1: unavailable, 0: ask using sysconf().
 .\" glibc defines it to 1.
 .SH "CONFORMING TO"

man2/mmap.2

@@ -126,7 +126,7 @@ You must specify exactly one of
 and 
 .BR MAP_PRIVATE .
 .LP
-The above three flags are described in POSIX.1b (formerly POSIX.4) and SUSv2.
+The above three flags are described in POSIX.1b and SUSv2.
 Linux also knows about the following non-standard flags:
 .TP
 .B MAP_DENYWRITE
@@ -344,7 +344,7 @@ or
 .\" jbl - not sure this actually happens ? see generic_file_mmap
 .\" mtk: Before 2.6.12, a length of 0 was permitted: mmap() did 
 .\" not create mapping, but just returned 'start'; since 2.6.12, 
-.\" a length of 0 yields EINVAL (as required by SUSv3).
+.\" a length of 0 yields EINVAL (as required by POSIX.1-2001).
 .TP
 .B ENFILE
 .\" This is for shared anonymous segments
@@ -396,13 +396,13 @@ are available,
 .B _POSIX_MAPPED_FILES
 is defined in <unistd.h> to a value greater than 0. (See also
 .BR sysconf (3).)
-.\" POSIX 1003.1-2001: It shall be defined to -1 or 0 or 200112L.
+.\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
 .\" -1: unavailable, 0: ask using sysconf().
 .\" glibc defines it to 1.
 .SH "CONFORMING TO"
-SVr4, POSIX.1b (formerly POSIX.4), 4.4BSD, SUSv2.
+SVr4, 4.4BSD, POSIX.1-2001.
-SVr4 documents additional error codes ENXIO and ENODEV.
+.\" SVr4 documents additional error codes ENXIO and ENODEV.
-SUSv2 documents additional error codes EMFILE and EOVERFLOW.
+.\" SUSv2 documents additional error codes EMFILE and EOVERFLOW.
 .SH BUGS
 On Linux there are no guarantees like those suggested above under 
 .BR MAP_NORESERVE . 

man2/mprotect.2

@@ -138,8 +138,9 @@ main(void)
 }
 .fi
 .SH "CONFORMING TO"
-SVr4, POSIX.1b (formerly POSIX.4).  SVr4 defines an additional error
+SVr4, POSIX.1-2001.
-code EAGAIN. The SVr4 error conditions don't map neatly onto Linux's.
+.\" SVr4 defines an additional error
+.\" code EAGAIN. The SVr4 error conditions don't map neatly onto Linux's.
 POSIX says that
 .BR mprotect ()
 can be used only on regions of memory obtained from

man2/msgctl.2

@@ -323,7 +323,8 @@ a recompilation under glibc-2.1.91 or later should suffice.
 (The kernel distinguishes old and new calls by an IPC_64 flag in
 .IR cmd .)
 .SH "CONFORMING TO"
-SVr4, SVID.  SVID does not document the EIDRM error condition.
+SVr4, POSIX.1-2001.
+.\" SVID does not document the EIDRM error condition.
 .SH "SEE ALSO"
 .BR msgget (2),
 .BR msgrcv (2),

man2/msgget.2

@@ -206,7 +206,8 @@ dependent
 The name choice IPC_PRIVATE was perhaps unfortunate, IPC_NEW
 would more clearly show its function.
 .SH "CONFORMING TO"
-SVr4, SVID.
+SVr4, POSIX.1-2001.
+.SH "LINUX NOTES"
 Until version 2.3.20 Linux would return EIDRM for a
 .BR msgget ()
 on a message queue scheduled for deletion.

man2/msgop.2

@@ -397,7 +397,7 @@ was specified in
 .I msgflg
 and no message of the requested type existed on the message queue.
 .SH "CONFORMING TO"
-SVr4, SVID, SUSv3.
+SVr4, POSIX.1-2001.
 .SH NOTES
 The 
 .I msgp

man2/msync.2

@@ -77,11 +77,11 @@ and
 .B _POSIX_SYNCHRONIZED_IO
 are defined in <unistd.h> to a value greater than 0. (See also
 .BR sysconf (3).)
-.\" POSIX 1003.1-2001: It shall be defined to -1 or 0 or 200112L.
+.\" POSIX.1-2001: It shall be defined to -1 or 0 or 200112L.
 .\" -1: unavailable, 0: ask using sysconf().
 .\" glibc defines them to 1.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1-2001.
 
 This call was introduced in Linux 1.3.21, and then used EFAULT instead of
 ENOMEM. In Linux 2.4.19 this was changed to the POSIX value ENOMEM.

man2/nanosleep.2

@@ -142,7 +142,7 @@ If the system call is subsequently restarted,
 then the time that the process spent in the stopped state is 
 \fInot\fP counted against the sleep interval.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4).
+POSIX.1-2001.
 .SH "SEE ALSO"
 .BR sched_setscheduler (2),
 .BR timer_create (2),

man2/nice.2

@@ -65,11 +65,12 @@ capability is required.
 resource limit in
 .BR setrlimit (2).)
 .SH "CONFORMING TO"
-SVr4, SVID EXT, AT&T, X/OPEN, 4.3BSD. However, the Linux and (g)libc
+SVr4, 4.3BSD, POSIX.1-2001. 
+However, the Linux and (g)libc
 (earlier than glibc 2.2.4) return value is nonstandard, see below.
 SVr4 documents an additional EINVAL error code.
 .SH NOTES
-SUSv2 and POSIX 1003.1-2003 specify that
+SUSv2 and POSIX.1-2001 specify that
 .BR nice ()
 should return the new nice value.
 However, the Linux syscall and the

man2/open.2

@@ -482,7 +482,7 @@ This is typically used to open devices in order to get a file descriptor
 for use with
 .BR ioctl (2).
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD.
+SVr4, 4.3BSD, POSIX.1-2001.
 The
 .BR O_NOATIME ,
 .BR O_NOFOLLOW ,

man2/pause.2

@@ -60,7 +60,7 @@ is set to
 .B EINTR
 a signal was caught and the signal-catching function returned.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, 4.3BSD
+SVr4, 4.3BSD, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR kill (2),
 .BR select (2),

man2/pipe.2

@@ -59,7 +59,7 @@ Too many file descriptors are in use by the process.
 .B ENFILE
 The system limit on the total number of open files has been reached.
 .SH "CONFORMING TO"
-POSIX.1
+POSIX.1-2001.
 .SH EXAMPLE
 .\" fork.2 refers to this example program.
 The following program creates a pipe, and then 

man2/posix_fadvise.2

@@ -106,10 +106,14 @@ Pages that have not yet been written out will be unaffected, so if the
 application wishes to guarantee that pages will be released, it should
 call \fBfsync\fP() or \fBfdatasync\fP() first.
 .SH "CONFORMING TO"
-SUSv3 (Advanced Realtime Option), POSIX 1003.1-2003.
+POSIX.1-2001.
 Note that the type of the
 .I len
-parameter was changed from size_t to off_t in POSIX 1003.1-2003 TC5.
+parameter was changed from 
+.I size_t 
+to 
+.I off_t 
+in POSIX.1-2003 TC5.
 .SH BUGS
 In kernels before 2.6.6, if 
 .I len

man2/pread.2

@@ -75,7 +75,7 @@ can fail and set
 .I errno
 to any error specified for \fBwrite\fR(2) or \fBlseek\fR(2).
 .SH "CONFORMING TO"
-Unix98
+POSIX.1-2001.
 .SH HISTORY
 The \fBpread\fR() and \fBpwrite\fR() system calls were added to Linux in
 version 2.1.60; the entries in the i386 system call table were added

man2/ptrace.2

@@ -410,7 +410,7 @@ Alternatively, the process may already be being traced, or be
 The specified process does not exist, or is not currently being traced 
 by the caller, or is not stopped (for requests that require that).
 .SH "CONFORMING TO"
-SVr4, SVID EXT, AT&T, X/OPEN, 4.3BSD
+SVr4, 4.3BSD
 .SH "SEE ALSO"
 .BR gdb (1),
 .BR strace (1),

man2/read.2

@@ -118,7 +118,7 @@ to return \-1 (with
 .I errno
 set to EINTR) or to return the number of bytes already read.
 .SH "CONFORMING TO"
-SVr4, SVID, AT&T, POSIX, X/OPEN, 4.3BSD
+SVr4, 4.3BSD, POSIX.1-2001.
 .SH RESTRICTIONS
 On NFS file systems, reading small amounts of data will only update the
 time stamp the first time, subsequent calls may not do so.  This is caused

man2/readlink.2

@@ -97,9 +97,10 @@ Insufficient kernel memory was available.
 .B ENOTDIR
 A component of the path prefix is not a directory.
 .SH "CONFORMING TO"
-X/OPEN, 4.4BSD (the
+4.4BSD (the
 .BR readlink ()
-function call appeared in 4.2BSD).
+function call appeared in 4.2BSD),
+POSIX.1-2001.
 .SH HISTORY
 In versions of glibc up to and including glibc 2.4, the return type of
 .BR readlink ()

man2/readv.2

@@ -112,14 +112,14 @@ permitted maximum.
 .BR readv ()
 and
 .BR writev ()
-functions first appeared in 4.2BSD), Unix98, POSIX 1003.1-2001.
+functions first appeared in 4.2BSD), POSIX.1-2001.
 Linux libc5 used \fIsize_t\fR as the type of the \fIcount\fR parameter,
 and \fIint\fP as return type for these functions.
 .\" The readv/writev system calls were buggy before Linux 1.3.40.
 .\" (Says release.libc.)
 .SH "LINUX NOTES"
-SUSv3 allows an implementation to place a limit on the number of items
+POSIX.1-2001 allows an implementation to place a limit on 
-that can be passed in
+the number of items that can be passed in
 .IR vector .
 An implementation can advertise its limit by defining
 .B IOV_MAX

man2/reboot.2

@@ -142,7 +142,8 @@ the
 capability is required.
 .SH "CONFORMING TO"
 .BR reboot ()
-is Linux specific, and should not be used in programs intended to be portable.
+is Linux specific, 
+and should not be used in programs intended to be portable.
 .SH "SEE ALSO"
 .BR sync (2),
 .BR bootparam (7),

man2/recv.2

@@ -389,9 +389,9 @@ The argument
 does not refer to a socket.
 .SH "CONFORMING TO"
 4.4BSD (these function calls first appeared in 4.2BSD),
-POSIX 1003.1-2001.
+POSIX.1-2001.
 .LP
-POSIX only describes the
+POSIX.1-2001 only describes the
 .BR MSG_OOB ,
 .BR MSG_PEEK ,
 and

man2/rename.2

@@ -197,7 +197,7 @@ are not on the same mounted filesystem.
 does not work across different mount points,
 even if the same filesystem is mounted on both.)
 .SH "CONFORMING TO"
-POSIX, 4.3BSD, ANSI C
+4.3BSD, C89, POSIX.1-2001.
 .SH BUGS
 On NFS filesystems, you can not assume that if the operation
 failed the file was not renamed.  If the server does the rename operation

man2/rmdir.2

@@ -121,7 +121,7 @@ does not support the removal of directories.
 .I pathname
 refers to a file on a read-only filesystem.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, 4.3BSD
+SVr4, 4.3BSD, POSIX.1-2001.
 .SH BUGS
 Infelicities in the protocol underlying NFS can cause the unexpected
 disappearance of directories which are still being used.

man2/sched_get_priority_max.2

@@ -93,7 +93,7 @@ is set appropriately.
 .B EINVAL
 The parameter \fIpolicy\fR does not identify a defined scheduling policy.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1-2001.
 .SH "SEE ALSO"
 .BR sched_getaffinity (2),
 .BR sched_getparam (2),
@@ -104,8 +104,3 @@ POSIX.1b (formerly POSIX.4)
 .PP
 .I Programming for the real world \- POSIX.4
 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0
-.br
-.I IEEE Std 1003.1b-1993
-(POSIX.1b standard)
-.br
-.I ISO/IEC 9945-1:1996

man2/sched_rr_get_interval.2

@@ -82,7 +82,7 @@ The system call is not yet implemented.
 .B ESRCH
 The process whose ID is \fIpid\fR could not be found.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1-2001.
 .SH BUGS
 As of Linux 1.3.81 \fBsched_rr_get_interval\fR() returns with error
 ENOSYS, because SCHED_RR has not yet been fully implemented and tested
@@ -93,8 +93,3 @@ has a description of the Linux scheduling scheme.
 .PP
 .I Programming for the real world \- POSIX.4
 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0
-.br
-.I IEEE Std 1003.1b-1993
-(POSIX.1b standard, formerly POSIX.4)
-.br
-.I ISO/IEC 9945-1:1996

man2/sched_setparam.2

@@ -103,7 +103,7 @@ capability).
 .B ESRCH
 The process whose ID is \fIpid\fR could not be found.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1-2001.
 .SH "SEE ALSO"
 .BR getpriority (2),
 .BR nice (2),
@@ -118,8 +118,3 @@ POSIX.1b (formerly POSIX.4)
 .PP
 .I Programming for the real world \- POSIX.4
 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0
-.br
-.I IEEE Std 1003.1b-1993
-(POSIX.1b standard)
-.br
-.I ISO/IEC 9945-1:1996

man2/sched_setscheduler.2

@@ -129,7 +129,7 @@ will be inserted at the end of the list for its priority. A call to
 \fIpid\fP at the start of the list if it was runnable.
 As a consequence, it may preempt the currently running process if
 it has the same priority.
-(POSIX 1003.1 specifies that the process should go to the end
+(POSIX.1 specifies that the process should go to the end
 of the list.)
 .\" In 2.2.x and 2.4.x, the process is placed at the front of the queue
 .\" In 2.0.x, the Right Thing happened: the process went to the back -- MTK
@@ -288,7 +288,7 @@ The calling process does not have appropriate privileges.
 .B ESRCH
 The process whose ID is \fIpid\fP could not be found.
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4).
+POSIX.1-2001.
 The \fISCHED_BATCH\fP policy is Linux specific.
 .SH NOTES
 Standard Linux is a general-purpose operating system
@@ -337,11 +337,3 @@ designed specifically for hard real-time applications.
 .PP
 .I Programming for the real world \- POSIX.4
 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0
-.br
-.I IEEE Std 1003.1b-1993
-(POSIX.1b standard)
-.br
-.I ISO/IEC 9945-1:1996
-\- This is the new 1996 revision of POSIX.1 which contains in one
-single standard POSIX.1(1990), POSIX.1b(1993), POSIX.1c(1995), and
-POSIX.1i(1995).

man2/sched_yield.2

@@ -61,15 +61,10 @@ On error, \-1 is returned, and
 is set appropriately.
 
 .SH "CONFORMING TO"
-POSIX.1b (formerly POSIX.4)
+POSIX.1-2001.
 .SH "SEE ALSO"
 .BR sched_setscheduler (2)
 for a description of Linux scheduling.
 .PP
 .I Programming for the real world \- POSIX.4
 by Bill O. Gallmeister, O'Reilly & Associates, Inc., ISBN 1-56592-074-0
-.br
-.I IEEE Std 1003.1b-1993
-(POSIX.1b standard)
-.br
-.I ISO/IEC 9945-1:1996

man2/select.2

@@ -40,7 +40,7 @@
 select, pselect, FD_CLR, FD_ISSET, FD_SET, FD_ZERO \- synchronous I/O multiplexing
 .SH SYNOPSIS
 .nf
-/* According to POSIX 1003.1-2001 */
+/* According to POSIX.1-2001 */
 .br
 .B #include <sys/select.h>
 .sp
@@ -235,7 +235,7 @@ struct timespec {
 .fi
 .in -0.25i
 
-(However, see below on the POSIX 1003.1-2001 versions.)
+(However, see below on the POSIX.1-2001 versions.)
 .PP
 Some code calls
 .BR select ()
@@ -337,6 +337,8 @@ main(void) {
 }
 .fi
 .SH "CONFORMING TO"
+.BR select () 
+conforms to POSIX.1-2001 and 
 4.4BSD 
 .RB ( select ()
 first appeared in 4.2BSD).  Generally portable to/from
@@ -345,8 +347,8 @@ System V variants).  However, note that the System V variant typically
 sets the timeout variable before exit, but the BSD variant does not.
 .PP
 .BR pselect ()
-is defined in IEEE Std 1003.1g-2000 (POSIX.1g), and in
+is defined in POSIX.1g, and in
-POSIX 1003.1-2001.
+POSIX.1-2001.
 .SH NOTES
 An 
 .I fd_set 
@@ -368,7 +370,7 @@ the two fields of a
 structure are longs (as shown above),
 and the structure is defined in
 .IR <sys/time.h> .
-The POSIX 1003.1-2001 situation is
+The POSIX.1-2001 situation is
 
 .RS
 .nf
@@ -393,7 +395,7 @@ include
 .I <time.h>
 for
 .BR select ().
-The POSIX 1003.1-2001 situation is that one should include
+The POSIX.1-2001 situation is that one should include
 .I <sys/select.h>
 for
 .BR select ()
@@ -411,7 +413,7 @@ when
 is defined, under glibc 2.2.2-2.2.4 it gives it when
 .B _XOPEN_SOURCE
 is defined and has a value of 600 or larger.
-No doubt, since POSIX 1003.1-2001, it should give the prototype by default.
+No doubt, since POSIX.1-2001, it should give the prototype by default.
 .SH VERSIONS
 .BR pselect ()
 was added to Linux in kernel 2.6.16.

man2/semctl.2

@@ -500,7 +500,8 @@ Under Linux,
 is not a system call, but is implemented via the system call
 .BR ipc (2).
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents more error conditions EINVAL and EOVERFLOW.
+SVr4, POSIX.1-2001.
+.\" SVr4 documents more error conditions EINVAL and EOVERFLOW.
 .SH "SEE ALSO"
 .BR ipc (2),
 .BR semget (2),

man2/semget.2

@@ -273,9 +273,9 @@ in the associated data structure retrieved by a
 .B IPC_STAT
 operation can be used to avoid races.)
 .SH "CONFORMING TO"
-SVr4, SVID.
+SVr4, POSIX.1-2001.
-SVr4 documents additional error conditions EFBIG, E2BIG, EAGAIN,
+.\" SVr4 documents additional error conditions EFBIG, E2BIG, EAGAIN,
-ERANGE, EFAULT.
+.\" ERANGE, EFAULT.
 .SH "SEE ALSO"
 .BR semctl (2),
 .BR semop (2),

man2/semop.2

@@ -474,8 +474,8 @@ This bug is fixed in kernel 2.6.11.
 .\" the fix:
 .\" http://marc.theaimsgroup.com/?l=linux-kernel&m=110261701025794&w=2
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents additional error conditions EINVAL, EFBIG,
+SVr4, POSIX.1-2001.
-ENOSPC.
+.\" SVr4 documents additional error conditions EINVAL, EFBIG, ENOSPC.
 .SH "SEE ALSO"
 .BR semctl (2),
 .BR semget (2),

man2/send.2

@@ -328,10 +328,10 @@ unless
 .B MSG_NOSIGNAL 
 is set.
 .SH "CONFORMING TO"
-4.4BSD, SVr4, POSIX 1003.1-2001.
+4.4BSD, SVr4, POSIX.1-2001.
 These function calls appeared in 4.2BSD.
 .LP
-POSIX only describes the
+POSIX.1-2001 only describes the
 .B MSG_OOB
 and
 .B MSG_EOR

man2/seteuid.2

@@ -88,7 +88,7 @@ and hence does not change the saved set-user-ID.
 Similar remarks hold for
 .BR setegid ().
 .SH "CONFORMING TO"
-4.3BSD
+4.3BSD, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR geteuid (2),
 .BR setresuid (2),

man2/setfsgid.2

@@ -69,7 +69,8 @@ is returned.  On error, the current value of
 is returned.
 .SH "CONFORMING TO"
 .BR setfsgid ()
-is Linux specific and should not be used in programs intended to be portable.
+is Linux specific and should not be used in programs intended 
+to be portable.
 It is present since Linux 1.1.44 and in libc since libc 4.7.6.
 .SH BUGS
 No error messages of any kind are returned to the caller. At the very

man2/setfsuid.2

@@ -69,7 +69,8 @@ is returned.  On error, the current value of
 is returned.
 .SH "CONFORMING TO"
 .BR setfsuid ()
-is Linux specific and should not be used in programs intended to be portable.
+is Linux specific and should not be used in programs intended 
+to be portable.
 It is present since Linux 1.1.44 and in libc since libc 4.7.6.
 .SH BUGS
 No error messages of any kind are returned to the caller. At the very

man2/setgid.2

@@ -58,7 +58,7 @@ CAP_SETGID capability), and
 does not match the effective group ID or saved set-group-ID of
 the calling process.
 .SH "CONFORMING TO"
-SVr4, SVID.
+SVr4, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR getgid (2),
 .BR setegid (2),

man2/setpgid.2

@@ -166,7 +166,7 @@ The functions
 .BR setpgid ()
 and
 .BR getpgrp ()
-conform to POSIX.1.
+conform to POSIX.1-2001.
 The function
 .BR setpgrp ()
 is from 4.2BSD.

man2/setresuid.2

@@ -77,7 +77,8 @@ bring that user ID over its NPROC rlimit.
 The calling process is not privileged (did not have the CAP_SETUID
 capability) and tried to change the IDs to values that are not permitted.
 .SH "CONFORMING TO"
-This call is nonstandard.
+These calls are non-standard; 
+they also appear on HP-UX and some of the BSDs.
 .SH HISTORY
 This system call was first introduced in HP-UX.
 It is available under Linux since Linux 2.1.44.

man2/setreuid.2

@@ -103,7 +103,7 @@ Setting the effective user (group) ID to the
 saved set-user-ID (saved set-group-ID) is
 possible since Linux 1.1.37 (1.1.38).
 .SH "CONFORMING TO"
-4.3BSD (the
+POSIX.1-2001, 4.3BSD (the
 .BR setreuid ()
 and
 .BR setregid ()

man2/setsid.2

@@ -70,7 +70,7 @@ and
 and have the child do
 .BR setsid ().
 .SH "CONFORMING TO"
-POSIX, SVr4.
+SVr4, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR setpgid (2),
 .BR setpgrp (2),

man2/setuid.2

@@ -82,9 +82,10 @@ capability) and
 .I uid
 does not match the real UID or saved set-user-ID of the calling process.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX.1.  Not quite compatible with the 4.4BSD call, which
+SVr4, POSIX.1-2001.  
-sets all of the real, saved, and effective user IDs.  SVr4 documents an
+Not quite compatible with the 4.4BSD call, which
-additional EINVAL error condition.
+sets all of the real, saved, and effective user IDs.  
+.\" SVr4 documents an additional EINVAL error condition.
 .SH "LINUX-SPECIFIC REMARKS"
 Linux has the concept of filesystem user ID, normally equal to the
 effective user ID.  The

man2/shmctl.2

@@ -380,9 +380,10 @@ a recompilation under glibc-2.1.91 or later should suffice.
 (The kernel distinguishes old and new calls by an IPC_64 flag in
 .IR cmd .)
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents additional error conditions EINVAL,
+SVr4, POSIX.1-2001.  
-ENOENT, ENOSPC, ENOMEM, EEXIST.  Neither SVr4 nor SVID documents
+.\" SVr4 documents additional error conditions EINVAL,
-an EIDRM error condition.
+.\" ENOENT, ENOSPC, ENOMEM, EEXIST.  Neither SVr4 nor SVID documents
+.\" an EIDRM error condition.
 .SH "SEE ALSO"
 .BR mlock (2),
 .BR setrlimit (2),

man2/shmget.2

@@ -286,7 +286,9 @@ number of shared memory segments
 The name choice IPC_PRIVATE was perhaps unfortunate, IPC_NEW
 would more clearly show its function.
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents an additional error condition EEXIST.
+SVr4, POSIX.1-2001.  
+.\" SVr4 documents an additional error condition EEXIST.
+.SH LINUX NOTES
 Until version 2.3.30 Linux would return EIDRM for a
 .BR shmget ()
 on a shared memory segment scheduled for deletion.

man2/shmop.2

@@ -269,8 +269,11 @@ The implementation places no intrinsic limit on the per\-process maximum
 number of shared memory segments
 .RB ( SHMSEG ).
 .SH "CONFORMING TO"
-SVr4, SVID.  SVr4 documents an additional error condition EMFILE.
+SVr4, POSIX.1-2001.  
-In SVID-v4 the type of the \fIshmaddr\fP argument was changed from
+.\" SVr4 documents an additional error condition EMFILE.
+
+In SVID 3 (or perhaps earlier) 
+the type of the \fIshmaddr\fP argument was changed from
 .B "char *"
 into
 .BR "const void *" ,

man2/sigaction.2

@@ -469,7 +469,8 @@ execution of the handler, but also the signals specified in
 .IR sa_mask .
 This bug is was fixed in kernel 2.6.14.
 .SH "CONFORMING TO"
-POSIX, SVr4.  SVr4 does not document the EINTR condition.
+POSIX.1-2001, SVr4.  
+.\" SVr4 does not document the EINTR condition.
 .SH UNDOCUMENTED
 Before the introduction of
 .B SA_SIGINFO

man2/sigaltstack.2

@@ -181,7 +181,7 @@ All new applications should be written using \fBsigaltstack\fP().
 different struct, and had the major disadvantage that the caller
 had to know the direction of stack growth.
 .SH "CONFORMING TO"
-SUSv2, SVr4, POSIX 1003.1-2001.
+SUSv2, SVr4, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR execve (2),
 .BR setrlimit (2),

man2/signal.2

@@ -122,7 +122,7 @@ If a signal interrupts an unsafe function, and
 .I handler
 calls an unsafe function, then the behavior is undefined. Safe
 functions are listed explicitly in the various standards.
-The POSIX 1003.1-2003 list is
+The POSIX.1-2003 list is
 
 _Exit()
 _exit()
@@ -280,7 +280,7 @@ and, when
 is defined, also
 .IR sighandler_t .
 .SH "CONFORMING TO"
-ANSI C
+C89, POSIX.1-2001.
 .SH "SEE ALSO"
 .BR kill (1),
 .BR alarm (2),

man2/sigqueue.2

@@ -105,7 +105,7 @@ having it unblocked, or by waiting for it using
 then at least some signal must be delivered to this thread before this
 function returns.
 .SH "CONFORMING TO"
-POSIX 1003.1-2001
+POSIX.1-2001
 .SH "SEE ALSO"
 .BR kill (2),
 .BR sigaction (2),

man2/sigwaitinfo.2

@@ -137,7 +137,7 @@ as a call to
 .BR sigwaitinfo (),
 and indeed this is what is done on Linux.
 .SH "CONFORMING TO"
-POSIX 1003.1-2001
+POSIX.1-2001
 .SH "SEE ALSO"
 .BR kill (2),
 .BR sigaction (2),

man2/socket.2

@@ -301,7 +301,7 @@ supported within this domain.
 .PP
 Other errors may be generated by the underlying protocol modules.
 .SH "CONFORMING TO"
-4.4BSD, SUSv2, POSIX 1003.1-2001.
+4.4BSD, POSIX.1-2001.
 .BR socket ()
 appeared in 4.2BSD. It is generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including

man2/socketpair.2

@@ -86,7 +86,7 @@ The specified protocol does not support creation of socket pairs.
 .B EPROTONOSUPPORT
 The specified protocol is not supported on this machine.
 .SH "CONFORMING TO"
-4.4BSD, SUSv2, POSIX 1003.1-2001.
+4.4BSD, POSIX.1-2001.
 The
 .BR socketpair ()
 function call appeared in 4.2BSD. It is generally portable to/from

man2/stat.2

@@ -306,34 +306,30 @@ Out of memory (i.e. kernel memory).
 .B ENOTDIR
 A component of the path is not a directory.
 .SH "CONFORMING TO"
-The
+calls conform to SVr4, 4.3BSD, POSIX.1-2001.
-.BR stat ()
+.\" SVr4 documents additional
-and
+.\" .BR fstat ()
-.BR fstat ()
+.\" error conditions EINTR, ENOLINK, and EOVERFLOW.  SVr4
-calls conform to SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  The
+.\" documents additional
-.BR lstat ()
+.\" .BR stat ()
-call conforms to 4.3BSD and SVr4.
+.\" and
-SVr4 documents additional
+.\" .BR lstat ()
-.BR fstat ()
+.\" error conditions EINTR, EMULTIHOP, ENOLINK, and EOVERFLOW.
-error conditions EINTR, ENOLINK, and EOVERFLOW.  SVr4
+
-documents additional
-.BR stat ()
-and
-.BR lstat ()
-error conditions EINTR, EMULTIHOP, ENOLINK, and EOVERFLOW.
 Use of the
 .I st_blocks
 and
 .I st_blksize
 fields may be less portable. (They were introduced in BSD.
-Are not specified by POSIX. The interpretation differs between
+The interpretation differs between
 systems, and possibly on a single system when NFS mounts are involved.)
 .LP
 POSIX does not describe the S_IFMT, S_IFSOCK, S_IFLNK, S_IFREG, S_IFBLK,
 S_IFDIR, S_IFCHR, S_IFIFO, S_ISVTX bits, but instead demands the use of
-the macros S_ISDIR(), etc. The S_ISLNK and S_ISSOCK macros are not in
+the macros S_ISDIR(), etc. 
-POSIX.1-1996, but both will be in the next POSIX standard;
+The S_ISLNK and S_ISSOCK macros are not in
-the former is from SVID 4v2, the latter from SUSv2.
+POSIX.1-1996, but both are present in POSIX.1-2001;
+the former is from SVID 4, the latter from SUSv2.
 .LP
 Unix V7 (and later systems) had S_IREAD, S_IWRITE, S_IEXEC, where POSIX
 prescribes the synonyms S_IRUSR, S_IWUSR, S_IXUSR.

man2/statfs.2

@@ -212,7 +212,7 @@ that returns a
 containing an
 .I "unsigned long"
 .IR f_fsid .
-Linux, SunOS, HPUX, 4.4BSD have a system call
+Linux, SunOS, HP-UX, 4.4BSD have a system call
 .BR statfs ()
 that returns a
 .I "struct statfs"

man2/statvfs.2

@@ -152,7 +152,7 @@ is not a directory.
 Some values were too large to be represented in the returned struct.
 .PP
 .SH "CONFORMING TO"
-Solaris, Irix, POSIX 1003.1-2001
+Solaris, Irix, POSIX.1-2001
 .SH NOTES
 The Linux kernel has system calls 
 .BR statfs ()

man2/stime.2

@@ -55,7 +55,7 @@ Under Linux the
 .B CAP_SYS_TIME
 privilege is required.
 .SH "CONFORMING TO"
-SVr4, SVID, X/OPEN
+SVr4.
 .SH NOTES
 Under glibc2,
 .I <time.h>