Classical BSD versions are now always named x.yBSD (formerly

there was a mix of x.yBSD and BSD x.y).

Changes

@@ -20,6 +20,9 @@ Global changes
 The terms "set-user-ID" and "set-group-ID" are now used consistently
 (no abbreviations) accorss all manual pages.
 
+Classical BSD versions are now always named x.yBSD (formerly
+there was a mix of x.yBSD and BSD x.y).
+
 Typographical or grammatical errors have been corrected in several
 places.
 

man1/install.1

@@ -178,7 +178,7 @@ The variables LANG, LC_ALL, LC_CTYPE and LC_MESSAGES have the
 usual meaning. For the GNU version, the variables SIMPLE_BACKUP_SUFFIX
 and VERSION_CONTROL control backup file naming, as described above.
 .SH "CONFORMING TO"
-BSD 4.2 (which had the \-c, \-m, \-o, \-g and \-s options).
+4.2BSD (which had the \-c, \-m, \-o, \-g and \-s options).
 .SH NOTES
 This page describes
 .B install

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, BSD 4.3.
+SVr4, SVID, POSIX, X/OPEN, 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

@@ -272,7 +272,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 BSD 4.*, SunOS 4, SGI); a POSIX 1003.1g draft
+and on many other systems like 4.x BSD, SunOS 4, SGI); a POSIX 1003.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, BSD 4.3
+SVID, AT&T, POSIX, X/OPEN, 4.3BSD
 .SH "SEE ALSO"
 .BR chmod (2),
 .BR chown (2),

man2/alarm.2

@@ -73,7 +73,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, BSD 4.3
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD
 .SH "SEE ALSO"
 .BR gettimeofday (2),
 .BR pause (2),

man2/bind.2

@@ -187,7 +187,7 @@ The transparent proxy options are not described.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (the
 .BR bind ()
-function first appeared in BSD 4.2).  SVr4 documents additional
+function first appeared in 4.2BSD).  SVr4 documents additional
 .BR EADDRNOTAVAIL , 
 .BR EADDRINUSE , 
 and
@@ -203,7 +203,7 @@ The third argument of
 .BR bind ()
 is in reality an
 .I int
-(and this is what BSD 4.* and libc4 and libc5 have).
+(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.

man2/brk.2

@@ -65,7 +65,7 @@ and
 is set to
 .BR ENOMEM .
 .SH "CONFORMING TO"
-BSD 4.3
+4.3BSD
 
 .BR brk " and " sbrk
 are not defined in the C Standard and are deliberately excluded from the

man2/close.2

@@ -79,7 +79,7 @@ call was interrupted by a signal.
 .B EIO
 An I/O error occurred.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, BSD 4.3.  SVr4 documents an additional
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  SVr4 documents an additional
 ENOLINK error condition.
 .SH NOTES
 Not checking the return value of close is a common but nevertheless

man2/connect.2

@@ -208,7 +208,7 @@ be very long when syncookies are enabled on the server.
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (the
 .BR connect ()
-function first appeared in BSD 4.2).  SVr4 documents the additional
+function first appeared in 4.2BSD).  SVr4 documents the additional
 general error codes 
 .BR EADDRNOTAVAIL , 
 .BR EINVAL , 
@@ -225,7 +225,7 @@ The third argument of
 .BR connect ()
 is in reality an
 .I int
-(and this is what BSD 4.* and libc4 and libc5 have).
+(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.

man2/dup.2

@@ -117,7 +117,7 @@ without closing
 .I newfd
 first.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, BSD 4.3. SVr4 documents additional
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD. SVr4 documents additional
 EINTR and ENOLINK error conditions.  POSIX.1 adds EINTR.
 The EBUSY return is Linux-specific.
 .SH "SEE ALSO"

man2/execve.2

@@ -172,7 +172,7 @@ 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, BSD 4.3.  POSIX does not document the #!  behavior
+SVr4, SVID, X/OPEN, 4.3BSD.  POSIX does not document the #!  behavior
 but is otherwise compatible.  SVr4 documents additional error
 conditions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not
 document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL,

man2/fcntl.2

@@ -864,7 +864,7 @@ 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, BSD 4.3.  Only the operations F_DUPFD,
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  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

man2/fork.2

@@ -81,7 +81,7 @@ failed to allocate the necessary kernel structures because memory is tight.
 .SH "CONFORMING TO"
 The
 .B fork
-call conforms to SVr4, SVID, POSIX, X/OPEN, BSD 4.3.
+call conforms to SVr4, SVID, POSIX, X/OPEN, 4.3BSD.
 .SH "SEE ALSO"
 .BR clone (2),
 .BR execve (2),

man2/getdtablesize.2

@@ -52,7 +52,7 @@ The libc4 and libc5 versions return
 .SH "CONFORMING TO"
 SVr4, 4.4BSD (the
 .B getdtablesize
-function first appeared in BSD 4.2).
+function first appeared in 4.2BSD).
 .SH "SEE ALSO"
 .BR close (2),
 .BR dup (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, BSD 4.3
+POSIX, 4.3BSD
 .SH "SEE ALSO"
 .BR setgid (2),
 .BR setregid (2)

man2/getpeername.2

@@ -90,7 +90,7 @@ function call first appeared in 4.2BSD).
 .SH NOTE
 The third argument of 
 .B getpeername
-is in reality an `int *' (and this is what BSD 4.* and libc4 and libc5 have).
+is in reality an `int *' (and this is what 4.x BSD and libc4 and libc5 have).
 Some POSIX confusion resulted in the present socklen_t, also used by glibc.
 See also
 .BR accept (2).

man2/getpid.2

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

man2/getpriority.2

@@ -147,7 +147,7 @@ all SYSV-like systems.
 Linux requires the real or effective user ID of the caller to match
 the real user of the process \fIwho\fP (instead of its effective user ID).
 All BSD-like systems (SunOS 4.1.3, Ultrix 4.2,
-BSD 4.3, FreeBSD 4.3, OpenBSD-2.5, ...) require
+4.3BSD, FreeBSD 4.3, OpenBSD-2.5, ...) require
 the effective user ID of the caller to match
 the real or effective user ID of the process \fIwho\fP.
 .LP

man2/getrlimit.2

@@ -330,7 +330,7 @@ signals delivered when a process encountered the soft and hard
 limits were delivered one (CPU) second later than they should have been.
 This was fixed in kernel 2.6.8.
 .SH "CONFORMING TO"
-SVr4, BSD 4.3.
+SVr4, 4.3BSD.
 .BR RLIMIT_MEMLOCK
 and 
 .BR RLIMIT_NPROC

man2/getrusage.2

@@ -88,7 +88,7 @@ points outside the accessible address space.
 .I who
 is invalid.
 .SH "CONFORMING TO"
-SVr4, BSD 4.3
+SVr4, 4.3BSD
 .SH NOTES
 Including
 .I <sys/time.h>
@@ -110,7 +110,7 @@ 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.
 .LP
-The above struct was taken from BSD 4.3 Reno.
+The above struct was taken from 4.3BSD Reno.
 Not all fields are meaningful under Linux.
 In linux 2.4 only the fields
 .IR ru_utime ,

man2/getsockname.2

@@ -88,7 +88,7 @@ and ENOSR error codes.
 .SH NOTE
 The third argument of 
 .B getsockname
-is in reality an `int *' (and this is what BSD 4.* and libc4 and libc5 have).
+is in reality an `int *' (and this is what 4.x BSD and libc4 and libc5 have).
 Some POSIX confusion resulted in the present socklen_t, also used by glibc.
 See also
 .BR accept (2).

man2/getsockopt.2

@@ -164,7 +164,7 @@ options
 .SH NOTE
 The fifth argument of 
 .BR getsockopt " and " setsockopt
-is in reality an int [*] (and this is what BSD 4.* and libc4 and libc5 have).
+is in reality an int [*] (and this is what 4.x BSD and libc4 and libc5 have).
 Some POSIX confusion resulted in the present socklen_t, also used by glibc.
 See also
 .BR accept (2).

man2/gettimeofday.2

@@ -217,7 +217,7 @@ _POSIX_SOURCE or compiling with the \-ansi flag).
 .LP
 Traditionally, the fields of struct timeval were longs.
 .SH "CONFORMING TO"
-SVr4, BSD 4.3. POSIX 1003.1-2001 describes gettimeofday()
+SVr4, 4.3BSD. POSIX 1003.1-2001 describes gettimeofday()
 but not settimeofday().
 .SH "SEE ALSO"
 .BR date (1),

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, BSD 4.3.
+POSIX, 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/kill.2

@@ -135,7 +135,7 @@ user ID of the receiver.
 The current rules, which conform to POSIX 1003.1-2001, were adopted
 in kernel 1.3.78.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX.1, X/OPEN, BSD 4.3, POSIX 1003.1-2001
+SVr4, SVID, POSIX.1, X/OPEN, 4.3BSD, POSIX 1003.1-2001
 .SH "SEE ALSO"
 .BR _exit (2),
 .BR killpg (2),

man2/link.2

@@ -152,7 +152,7 @@ Some other implementations behave in the same manner as Linux.
 .\" thread in the Austin mailing list reported that some
 .\" other (SysV) implementations did/do the same -- MTK, Apr 05
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, BSD 4.3, X/OPEN.  SVr4 documents additional ENOLINK and
+SVr4, SVID, POSIX, 4.3BSD, X/OPEN.  SVr4 documents additional ENOLINK and
 EMULTIHOP error conditions; POSIX.1 does not document ELOOP.
 X/OPEN does not document EFAULT, ENOMEM or EIO.
 .SH BUGS

man2/lseek.2

@@ -110,7 +110,7 @@ The resulting file offset cannot be represented in an off_t.
 .I fildes
 is associated with a pipe, socket, or FIFO.
 .SH "CONFORMING TO"
-SVr4, POSIX, BSD 4.3
+SVr4, POSIX, 4.3BSD
 .SH RESTRICTIONS
 Some devices are incapable of seeking and POSIX does not specify which
 devices must support it.

man2/nice.2

@@ -58,7 +58,7 @@ Under Linux the
 .B CAP_SYS_NICE
 capability is required.
 .SH "CONFORMING TO"
-SVr4, SVID EXT, AT&T, X/OPEN, BSD 4.3. However, the Linux and (g)libc
+SVr4, SVID EXT, AT&T, X/OPEN, 4.3BSD. 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

man2/open.2

@@ -444,7 +444,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, BSD 4.3.
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD.
 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, BSD 4.3
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD
 .SH "SEE ALSO"
 .BR kill (2),
 .BR select (2),

man2/ptrace.2

@@ -258,7 +258,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, BSD 4.3
+SVr4, SVID EXT, AT&T, X/OPEN, 4.3BSD
 .SH "SEE ALSO"
 .BR gdb (1),
 .BR strace (1),

man2/read.2

@@ -111,7 +111,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, BSD 4.3
+SVr4, SVID, AT&T, POSIX, X/OPEN, 4.3BSD
 .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/readv.2

@@ -112,7 +112,7 @@ the vector count \fIcount\fR is zero or greater than \fBMAX_IOVEC\fR.
 .B readv
 and
 .B writev
-functions first appeared in BSD 4.2), Unix98, POSIX 1003.1-2001.
+functions first appeared in 4.2BSD), Unix98, POSIX 1003.1-2001.
 Linux libc5 used \fBsize_t\fR as the type of the \fIcount\fR parameter,
 and \fBint\fP as return type for these functions.
 .\" The readv/writev system calls were buggy before Linux 1.3.40.

man2/recv.2

@@ -402,16 +402,16 @@ flags.
 .SH NOTE
 The prototypes given above follow glibc2.
 The Single Unix Specification agrees, except that it has return values
-of type `ssize_t' (while BSD 4.* and libc4 and libc5 all have `int').
+of type `ssize_t' (while 4.x BSD and libc4 and libc5 all have `int').
 The
 .I flags
-argument is `int' in BSD 4.*, but `unsigned int' in libc4 and libc5.
+argument is `int' in 4.x BSD, but `unsigned int' in libc4 and libc5.
 The
 .I len
-argument is `int' in BSD 4.*, but `size_t' in libc4 and libc5.
+argument is `int' in 4.x BSD, but `size_t' in libc4 and libc5.
 The
 .I fromlen
-argument is `int *' in BSD 4.*, libc4 and libc5.
+argument is `int *' in 4.x BSD, libc4 and libc5.
 The present  `socklen_t *' was invented by POSIX.
 See also
 .BR accept (2).

man2/rmdir.2

@@ -111,7 +111,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, BSD 4.3
+SVr4, SVID, POSIX, 4.3BSD
 .SH BUGS
 Infelicities in the protocol underlying NFS can cause the unexpected
 disappearance of directories which are still being used.

man2/send.2

@@ -340,13 +340,13 @@ flag is a Linux extension.
 The prototypes given above follow the Single Unix Specification,
 as glibc2 also does; the
 .I flags
-argument was `int' in BSD 4.*, but `unsigned int' in libc4 and libc5;
+argument was `int' in 4.x BSD, but `unsigned int' in libc4 and libc5;
 the
 .I len
-argument was `int' in BSD 4.* and libc4, but `size_t' in libc5;
+argument was `int' in 4.x BSD and libc4, but `size_t' in libc5;
 the
 .I tolen
-argument was `int' in BSD 4.* and libc4 and libc5.
+argument was `int' in 4.x BSD and libc4 and libc5.
 See also
 .BR accept (2).
 .SH BUGS

man2/seteuid.2

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

man2/setpgid.2

@@ -167,7 +167,7 @@ and
 conform to POSIX.1.
 The function
 .B setpgrp
-is from BSD 4.2.
+is from 4.2BSD.
 The function
 .B getpgid
 conforms to SVr4.

man2/setreuid.2

@@ -102,7 +102,7 @@ was specified.
 Setting the effective user (group) ID to the saved user ID is
 possible since Linux 1.1.37 (1.1.38).
 .SH "CONFORMING TO"
-BSD 4.3 (the
+4.3BSD (the
 .B setreuid
 and
 .B setregid

man2/sigaltstack.2

@@ -165,7 +165,7 @@ signal stack.
 For backwards compatibility, glibc also provides \fBsigstack\fP.
 All new applications should be written using \fBsigaltstack\fB.
 .SH HISTORY
-BSD 4.2 had a \fIsigstack\fP() system call. It used a slightly
+4.2BSD had a \fIsigstack\fP() system call. It used a slightly
 different struct, and had as major disadvantage that the caller
 had to know the direction of stack growth.
 .SH "CONFORMING TO"

man2/sigblock.2

@@ -95,7 +95,7 @@ or
 \- this restriction is silently imposed by the system.
 
 .SH "CONFORMING TO"
-4.4BSD. These function calls appeared in BSD 4.3 and are deprecated.
+4.4BSD. These function calls appeared in 4.3BSD and are deprecated.
 Use the POSIX signal facilities for new programs.
 .SH "SEE ALSO"
 .BR kill (2),

man2/socket.2

@@ -307,7 +307,7 @@ appeared in 4.2BSD. It is generally portable to/from
 non-BSD systems supporting clones of the BSD socket layer (including
 System V variants).
 .SH NOTE
-The manifest constants used under BSD 4.* for protocol families
+The manifest constants used under 4.x BSD for protocol families
 are PF_UNIX, PF_INET, etc., while AF_UNIX etc. are used for address
 families. However, already the BSD man page promises: "The protocol
 family generally is the same as the address family", and subsequent

man2/stat.2

@@ -288,7 +288,7 @@ The
 .BR stat ()
 and
 .BR fstat ()
-calls conform to SVr4, SVID, POSIX, X/OPEN, BSD 4.3.  The
+calls conform to SVr4, SVID, POSIX, X/OPEN, 4.3BSD.  The
 .BR lstat ()
 call conforms to 4.3BSD and SVr4.
 SVr4 documents additional

man2/symlink.2

@@ -137,8 +137,8 @@ file (unless it also has other hard links). If this behaviour is not
 desired, use
 .BR link .
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, BSD 4.3.  SVr4 documents additional error codes
-SVr4, SVID, BSD 4.3, X/OPEN.  SVr4 documents additional error codes
+SVr4, SVID, POSIX, 4.3BSD.  SVr4 documents additional error codes
+SVr4, SVID, 4.3BSD, X/OPEN.  SVr4 documents additional error codes
 EDQUOT and ENOSYS.
 See
 .BR open (2)

man2/sync.2

@@ -44,7 +44,7 @@ first commits inodes to buffers, and then buffers to disk.
 .SH ERRORS
 This function is always successful.
 .SH "CONFORMING TO"
-SVr4, SVID, X/OPEN, BSD 4.3
+SVr4, SVID, X/OPEN, 4.3BSD
 .SH BUGS
 According to the standard specification (e.g., SVID),
 \fBsync()\fP schedules the writes, but may return before the actual

man2/syscall.2

@@ -37,7 +37,7 @@
 .\"
 .Dd June 16, 1993
 .Dt SYSCALL 2
-.Os BSD 4
+.Os 4BSD
 .Sh NAME
 .Nm syscall
 .Nd indirect system call

man2/sysctl.2

@@ -128,7 +128,7 @@ A
 call has been present in Linux since version 1.3.57. It originated in
 4.4BSD. Only Linux has the
 .I /proc/sys
-mirror, and the object naming schemes differ between Linux and BSD 4.4,
+mirror, and the object naming schemes differ between Linux and 4.4BSD,
 but the declaration of the
 .BR sysctl (2)
 function is the same in both.

man2/time.2

@@ -64,9 +64,9 @@ required to be synchronised to a standard reference.  The intention is
 that the interpretation of seconds since the Epoch values be
 consistent; see POSIX.1 Annex B 2.2.2 for further rationale.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, BSD 4.3
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD
 .br
-Under BSD 4.3, this call is obsoleted by
+Under 4.3BSD, this call is obsoleted by
 .BR gettimeofday (2).
 POSIX does not specify any error conditions.
 .SH "SEE ALSO"

man2/times.2

@@ -154,7 +154,7 @@ that are not measured in clock ticks
 but in
 .BR CLOCKS_PER_SEC .
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, BSD 4.3
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD
 .SH "HISTORICAL NOTES"
 SVr1-3 returns
 .I long

man2/truncate.2

@@ -155,7 +155,7 @@ The
 .I fd
 does not reference a regular file.
 .SH "CONFORMING TO"
-4.4BSD, SVr4 (these function calls first appeared in BSD 4.2).
+4.4BSD, SVr4 (these function calls first appeared in 4.2BSD).
 POSIX 1003.1-1996 has
 .BR ftruncate .
 POSIX 1003.1-2001 also has

man2/umask.2

@@ -63,7 +63,7 @@ as 0666).
 This system call always succeeds and the previous value of the mask
 is returned.
 .SH "CONFORMING TO"
-SVr4, SVID, POSIX, X/OPEN, BSD 4.3
+SVr4, SVID, POSIX, X/OPEN, 4.3BSD
 .SH "SEE ALSO"
 .BR chmod (2),
 .BR mkdir (2),

man2/uname.2

@@ -69,7 +69,7 @@ is not valid.
 SVr4, SVID, POSIX, X/OPEN.
 There is no
 .B uname
-call in BSD 4.3.
+call in 4.3BSD.
 .PP
 The
 .I domainname

man2/utime.2

@@ -155,7 +155,7 @@ SVr4, SVID, POSIX.  SVr4 documents additional error conditions EFAULT,
 EINTR, ELOOP, EMULTIHOP, ENAMETOOLONG, ENOLINK, ENOLINK, ENOTDIR.
 .br
 .BR utimes :
-BSD 4.3
+4.3BSD
 .SH "SEE ALSO"
 .BR chattr (1),
 .BR stat (2)

man2/vfork.2

@@ -149,9 +149,9 @@ and requires a kernel patch.
 The
 .BR vfork ()
 system call appeared in 3.0BSD.
-.\" In the release notes for BSD 4.2 Sam Leffler wrote: `vfork: Is still
+.\" In the release notes for 4.2BSD Sam Leffler wrote: `vfork: Is still
 .\" present, but definitely on its way out'.
-In BSD 4.4 it was made synonymous to
+In 4.4BSD it was made synonymous to
 .BR fork ()
 but NetBSD introduced it again,
 cf. http://www.netbsd.org/Documentation/kernel/vfork.html .

man3/abort.3

@@ -47,7 +47,7 @@ function will still override it.
 .SH "RETURN VALUE"
 The \fBabort()\fP function never returns.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899 (C99)
+SVID 3, POSIX, 4.3BSD, ISO 9899 (C99)
 .SH "SEE ALSO"
 .BR sigaction (2),
 .BR exit (3),

man3/abs.3

@@ -55,7 +55,7 @@ appropriate integer type for the function.
 Returns the absolute value of the integer argument, of the appropriate
 integer type for the function.
 .SH "CONFORMING TO"
-SVID 3, POSIX.1, BSD 4.3, ISO/IEC 9899 (C99).  POSIX.1 (1996 edition) only
+SVID 3, POSIX.1, 4.3BSD, ISO/IEC 9899 (C99).  POSIX.1 (1996 edition) only
 requires the \fBabs()\fP function.  ISO/IEC 9899:1990 (C89) only
 includes the \fBabs()\fP and \fBlabs()\fP functions; the functions
 \fBllabs()\fP and \fBimaxabs()\fP were added in C99.

man3/acos.3

@@ -53,7 +53,7 @@ value is mathematically defined to be between 0 and PI (inclusive).
 .B EDOM
 \fIx\fP is out of range.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR asin (3),

man3/acosh.3

@@ -53,7 +53,7 @@ is set.
 .B EDOM
 \fIx\fP is out of range.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR asinh (3),

man3/alloca.3

@@ -60,7 +60,7 @@ If the allocation causes stack overflow, program behaviour is undefined.
 There is evidence that the
 .B alloca
 function appeared in 32v, pwb, pwb.2, 3bsd, and 4bsd.  There is a man page
-for it in BSD 4.3.  Linux uses the GNU version.
+for it in 4.3BSD.  Linux uses the GNU version.
 This function is not in POSIX or SUSv3.
 .SH "NOTES ON THE GNU VERSION"
 Normally,

man3/asin.3

@@ -56,7 +56,7 @@ value is mathematically defined to be between \-PI/2 and PI/2
 .B EDOM
 \fIx\fP is out of range.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acos (3),

man3/asinh.3

@@ -47,7 +47,7 @@ Link with \-lm.
 The \fBasinh()\fP function calculates the inverse hyperbolic sine of 
 \fIx\fP; that is the value whose hyperbolic sine is \fIx\fP.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acosh (3),

man3/atan.3

@@ -51,7 +51,7 @@ The \fBatan()\fP function returns the arc tangent in radians and the
 value is mathematically defined to be between \-PI/2 and PI/2
 (inclusive).
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acos (3),

man3/atan2.3

@@ -52,7 +52,7 @@ arguments are used to determine the quadrant of the result.
 The \fBatan2()\fP function returns the result in radians, which
 is between \-PI and PI (inclusive).
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acos (3),

man3/atanh.3

@@ -53,7 +53,7 @@ not-a-number (NaN) and \fIerrno\fP is set.
 .B EDOM
 \fIx\fP is out of range.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acosh (3),

man3/atexit.3

@@ -89,7 +89,7 @@ Functions registered using \fBatexit\fP() (and \fBon_exit\fP())
 are not called if a process terminates abnormally because
 of the delivery of a signal.
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, ISO 9899, POSIX 1003.1-2001
+SVID 3, 4.3BSD, ISO 9899, POSIX 1003.1-2001
 .SH "SEE ALSO"
 .BR _exit (3),
 .BR exit (3),

man3/atof.3

@@ -47,7 +47,7 @@ except that \fBatof()\fP does not detect errors.
 .SH "RETURN VALUE"
 The converted value.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899
+SVID 3, POSIX, 4.3BSD, ISO 9899
 .SH "SEE ALSO"
 .BR atoi (3),
 .BR atol (3),

man3/atoi.3

@@ -62,7 +62,7 @@ string to their return type of \fIlong\fP or \fIlong long\fP.
 .SH "RETURN VALUE"
 The converted value.
 .SH "CONFORMING TO"
-SVID 3, POSIX.1, BSD 4.3, ISO/IEC 9899.  ISO/IEC 9899:1990 (C89) and
+SVID 3, POSIX.1, 4.3BSD, ISO/IEC 9899.  ISO/IEC 9899:1990 (C89) and
 POSIX.1 (1996 edition) include the functions \fBatoi()\fP and
 \fBatol()\fP only; C99 adds the function \fBatoll()\fP.
 .SH NOTES

man3/bsearch.3

@@ -102,7 +102,7 @@ int main(int argc, char **argv) {
 .fi
 .\" this example referred to in qsort.3
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, ISO 9899 (C99)
+SVID 3, 4.3BSD, ISO 9899 (C99)
 .SH "SEE ALSO"
 .BR hsearch (3),
 .BR lsearch (3),

man3/byteorder.3

@@ -60,7 +60,7 @@ On the i80x86 the host byte order is Least Significant Byte first,
 whereas the network byte order, as used on the Internet, is Most 
 Significant Byte first.
 .SH "CONFORMING TO"
-BSD 4.3
+4.3BSD
 .SH "SEE ALSO"
 .BR gethostbyname (3),
 .BR getservent (3)

man3/ceil.3

@@ -59,7 +59,7 @@ of mantissa bits is 24 (resp. 53).)
 .SH "CONFORMING TO"
 The
 .B ceil()
-function conforms to SVID 3, POSIX, BSD 4.3, ISO 9899.
+function conforms to SVID 3, POSIX, 4.3BSD, ISO 9899.
 The other functions are from C99.
 .SH "SEE ALSO"
 .BR floor (3),

man3/closedir.3

@@ -51,7 +51,7 @@ is set appropriately.
 .B EBADF
 Invalid directory stream descriptor \fIdir\fP.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3
+SVID 3, POSIX, 4.3BSD
 .SH "SEE ALSO"
 .BR close (2),
 .BR opendir (3),

man3/copysign.3

@@ -48,7 +48,7 @@ If \fIx\fP is a NaN, then a NaN with the sign of \fIy\fP is returned.
 .SH NOTES
 The \fBcopysign()\fP functions may treat a negative zero as positive.
 .SH "CONFORMING TO"
-C99, BSD 4.3.
+C99, 4.3BSD.
 This function is defined in IEC 559 (and the appendix with
 recommended functions in IEEE 754/IEEE 854).
 .SH "SEE ALSO"

man3/cos.3

@@ -48,7 +48,7 @@ given in radians.
 .SH "RETURN VALUE"
 The \fBcos()\fP function returns a value between \-1 and 1.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and the long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acos (3),

man3/cosh.3

@@ -48,7 +48,7 @@ Link with \-lm.
 The \fBcosh()\fP function returns the hyperbolic cosine of \fIx\fP, which 
 is defined mathematically as (exp(x) + exp(\-x)) / 2.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899 (C99).
+SVID 3, POSIX, 4.3BSD, ISO 9899 (C99).
 The float and the long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR acosh (3),

man3/crypt.3

@@ -142,7 +142,7 @@ The entire key is significant here (instead of only the first
 .LP
 Programs using this function must be linked with \-lcrypt.
 .SH "CONFORMING TO"
-SVID, X/OPEN, BSD 4.3, POSIX 1003.1-2001
+SVID, X/OPEN, 4.3BSD, POSIX 1003.1-2001
 .SH "SEE ALSO"
 .BR login (1),
 .BR passwd (1),

man3/ctime.3

@@ -223,7 +223,7 @@ defined when _BSD_SOURCE was set before including
 .IR <time.h> .
 This is a BSD extension, present in 4.3BSD-Reno.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899
+SVID 3, POSIX, 4.3BSD, ISO 9899
 .SH "SEE ALSO"
 .BR date (1),
 .BR gettimeofday (2),

man3/daemon.3

@@ -85,4 +85,4 @@ need not be set.
 .SH HISTORY
 The
 .BR daemon ()
-function first appeared in BSD4.4.
+function first appeared in 4.4BSD.

man3/difftime.3

@@ -41,7 +41,7 @@ The two times are specified in calendar time, which represents the time
 elapsed since the Epoch
 (00:00:00 on January 1, 1970, Coordinated Universal Time (UTC)).
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, ISO 9899
+SVID 3, 4.3BSD, ISO 9899
 .SH NOTES
 This function is required by ANSI C.
 On a POSIX system, time_t is an arithmetic type, and one could just

man3/div.3

@@ -66,7 +66,7 @@ After
 .fi
 the values \fIq.quot\fP and \fIq.rem\fP are \-1 and \-2, respectively.
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, ISO 9899.
+SVID 3, 4.3BSD, ISO 9899.
 The functions lldiv() and imaxdiv() were added in ISO C99.
 .SH "SEE ALSO"
 .BR abs (3),

man3/erf.3

@@ -58,7 +58,7 @@ erf(x) = 2/sqrt(pi)* integral from 0 to x of exp(\-t*t) dt
 The \fBerfc()\fP function returns the complementary error function of
 \fIx\fP, that is 1.0 \- erf(x).
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, C99.
+SVID 3, 4.3BSD, C99.
 The float and long double variants are requirements of C99.
 .SH "SEE ALSO"
 .BR cerf (3),

man3/ether_aton.3

@@ -111,6 +111,6 @@ struct ether_addr {
 .SH BUGS
 The glibc 2.2.5 implementation of ether_line() is broken.
 .SH "CONFORMING TO"
-BSD 4.3, SunOS
+4.3BSD, SunOS
 .SH "SEE ALSO"
 .BR ethers (5)

man3/exit.3

@@ -54,7 +54,7 @@ termination, respectively.
 .SH "RETURN VALUE"
 The \fBexit\fP() function does not return.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899 (``ANSI C'')
+SVID 3, POSIX, 4.3BSD, ISO 9899 (``ANSI C'')
 .SH NOTES
 .LP
 It is undefined what happens if one of the

man3/exp.3

@@ -48,7 +48,7 @@ Link with \-lm.
 The \fBexp()\fP function returns the value of e (the base of natural
 logarithms) raised to the power of \fIx\fP.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and the long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR cbrt (3),

man3/exp2.3

@@ -48,7 +48,7 @@ Compile with \-std=c99; link with \-lm.
 The \fBexp2()\fP function returns the value of 2
 raised to the power of \fIx\fP.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and the long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR cbrt (3),

man3/fabs.3

@@ -50,7 +50,7 @@ No errors can occur.
 .SH "CONFORMING TO"
 The
 .B fabs()
-function conforms to SVID 3, POSIX, BSD 4.3, ISO 9899.
+function conforms to SVID 3, POSIX, 4.3BSD, ISO 9899.
 The other functions are from C99.
 .SH "SEE ALSO"
 .BR abs (3),

man3/ffs.3

@@ -57,7 +57,7 @@ arguments of possibly different size.
 These functions return the position of the first bit set,
 or 0 if no bits are set.
 .SH "CONFORMING TO"
-BSD 4.3, POSIX 1003.1-2001.
+4.3BSD, POSIX 1003.1-2001.
 .SH NOTES
 BSD systems have a prototype in
 .IR <string.h> .

man3/finite.3

@@ -81,7 +81,7 @@ is defined.
 .SH HISTORY
 The
 .B finite
-function occurs in BSD 4.3.
-.\" see IEEE.3 in the BSD 4.3 manual
+function occurs in 4.3BSD.
+.\" see IEEE.3 in the 4.3BSD manual
 .SH "SEE ALSO"
 .BR fpclassify (3)

man3/floor.3

@@ -59,7 +59,7 @@ of mantissa bits is 24 (resp. 53).)
 .SH "CONFORMING TO"
 The
 .B floor()
-function conforms to SVID 3, POSIX, BSD 4.3, ISO 9899.
+function conforms to SVID 3, POSIX, 4.3BSD, ISO 9899.
 The other functions are from C99.
 .SH "SEE ALSO"
 .BR ceil (3),

man3/fmod.3

@@ -55,7 +55,7 @@ when the function fails and \fIerrno\fP is set.
 .B EDOM
 The denominator \fIy\fP is zero.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and the long double variants are C99 requirements.
 .SH "SEE ALSO"
 .BR remainder (3)

man3/fpurge.3

@@ -67,7 +67,7 @@ is not an open stream.
 These functions are nonstandard and not portable.
 The function
 .IR fpurge ()
-was introduced in BSD 4.4 and is not available under Linux.
+was introduced in 4.4BSD and is not available under Linux.
 The function
 .IR __fpurge ()
 was introduced in Solaris, and is present in glibc 2.1.95 and later.

man3/frexp.3

@@ -54,7 +54,7 @@ times a power of two, and is always in the range 1/2 (inclusive) to
 1 (exclusive).  If \fIx\fP is zero, then the normalized fraction is
 zero and zero is stored in \fIexp\fP.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899.
+SVID 3, POSIX, 4.3BSD, ISO 9899.
 The float and the long double variants are C99 requirements.
 .SH EXAMPLE
 .nf

man3/ftime.3

@@ -79,7 +79,7 @@ The
 .B ftime()
 function appeared in 4.2BSD.
 .SH "CONFORMING TO"
-BSD 4.2, POSIX 1003.1-2001.
+4.2BSD, POSIX 1003.1-2001.
 .SH "SEE ALSO"
 .BR gettimeofday (2),
 .BR time (2)

man3/fts.3

@@ -748,7 +748,7 @@ The options were invalid.
 .Xr stat 2 ,
 .Xr qsort 3
 .Sh "CONFORMING TO"
-BSD 4.4. The
+4.4BSD. The
 .Nm fts
 utility is expected to be included in a future
 .St -p1003.1-88

man3/getenv.3

@@ -44,7 +44,7 @@ the form \fIname = value\fP.
 The \fBgetenv()\fP function returns a pointer to the value in the
 environment, or NULL if there is no match.
 .SH "CONFORMING TO"
-SVID 3, POSIX, BSD 4.3, ISO 9899
+SVID 3, POSIX, 4.3BSD, ISO 9899
 .SH "SEE ALSO"
 .BR clearenv (3),
 .BR putenv (3),

man3/getgrent.3

@@ -104,7 +104,7 @@ Insufficient buffer space supplied.
 .I /etc/group
 local group database file
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, POSIX 1003.1-2003.
+SVID 3, 4.3BSD, POSIX 1003.1-2003.
 .SH "SEE ALSO"
 .BR fgetgrent (3),
 .BR getgrent_r (3),

man3/getgrnam.3

@@ -158,7 +158,7 @@ Insufficient buffer space supplied.
 .I /etc/group
 local group database file
 .SH "CONFORMING TO"
-SVID 3, BSD 4.3, POSIX 1003.1-2003
+SVID 3, 4.3BSD, POSIX 1003.1-2003
 .SH NOTES
 The formulation given above under "RETURN VALUE" is from POSIX 1003.1-2001.
 It does not call "not found" an error, hence does not specify what value

man3/gethostbyname.3

@@ -232,7 +232,7 @@ resolver configuration file
 .I /etc/hosts
 host database file
 .SH "CONFORMING TO"
-BSD 4.3.
+4.3BSD.
 .SH "SYSV/POSIX EXTENSION"
 POSIX requires the
 .BR gethostent ()

man3/getloadavg.3

@@ -29,7 +29,7 @@
 .\"
 .Dd June 4, 1993
 .Dt GETLOADAVG 3
-.Os BSD 4.3
+.Os 4.3BSD
 .Sh NAME
 .Nm getloadavg
 .Nd get system load averages

man3/getmntent.3

@@ -146,7 +146,7 @@ SysV also has a \fBgetmntent()\fP function but the calling sequence
 differs, and the returned structure is different. Under SysV
 .I /etc/mnttab
 is used.
-BSD 4.4 and Digital Unix have a routine \fBgetmntinfo()\fP,
+4.4BSD and Digital Unix have a routine \fBgetmntinfo()\fP,
 a wrapper around the system call \fBgetfsstat()\fP.
 .SH "SEE ALSO"
 .BR fopen (3),