Removed HISTORY section, or moved it as a subsection or paragraphs

under another section e.g., NOTES.
This commit is contained in:
Michael Kerrisk 2007-05-18 11:59:14 +00:00
parent b32f7afa5b
commit 889829be48
32 changed files with 157 additions and 154 deletions

View File

@ -35,7 +35,7 @@ except that it terminates not only the present thread, but all threads
in the current thread group.
.SH "RETURN VALUE"
This system call does not return.
.SH HISTORY
.SH VERSIONS
This call is present since Linux 2.5.35.
.SH "CONFORMING TO"
This call is Linux specific.

View File

@ -55,8 +55,8 @@ or
int sz = getpagesize();
.fi
.RE
.SH HISTORY
This call first appeared in 4.2BSD.
.\" .SH HISTORY
.\" This call first appeared in 4.2BSD.
.SH CONFORMING TO
SVr4, 4.4BSD, SUSv2.
In SUSv2 the

View File

@ -44,7 +44,8 @@ returns the effective user ID of the current process.
These functions are always successful.
.SH "CONFORMING TO"
POSIX.1-2001, 4.3BSD.
.SH HISTORY
.SH NOTES
.SS History
In Unix V6 the
.BR getuid ()
call returned (euid << 8) + uid.

View File

@ -186,10 +186,10 @@ that are not mapped, the Linux version of
ignores them and applies the call to the rest (but returns
.B ENOMEM
from the system call, as it should).
.SH HISTORY
The
.BR madvise ()
function first appeared in 4.4BSD.
.\" .SH HISTORY
.\" The
.\" .BR madvise ()
.\" function first appeared in 4.4BSD.
.SH "CONFORMING TO"
POSIX.1b.
POSIX.1-2001 describes

View File

@ -146,10 +146,10 @@ is not specified in POSIX.1-2001,
and it is not available on all Unix implementations.
.\" It is on at least NetBSD, FreeBSD, OpenBSD, Solaris 8,
.\" AIX 5.1, SunOS 4.1
.SH HISTORY
The
.BR mincore ()
function first appeared in 4.4BSD.
.\" .SH HISTORY
.\" The
.\" .BR mincore ()
.\" function first appeared in 4.4BSD.
.SH VERSIONS
Available since Linux 2.3.99pre1 and glibc 2.2.
.SH "SEE ALSO"

View File

@ -387,7 +387,8 @@ The caller does not have the required privileges.
.SH "CONFORMING TO"
These functions are Linux specific and should not be used in
programs intended to be portable.
.SH HISTORY
.SH NOTES
.SS Linux Notes
The original
.BR umount ()
function was called as \fIumount(device)\fP and would return ENOTBLK

View File

@ -134,7 +134,7 @@ insanity.
.SH "CONFORMING TO"
.BR pivot_root ()
is Linux specific and hence is not portable.
.SH HISTORY
.SH VERSIONS
.BR pivot_root ()
was introduced in Linux 2.3.41.
.SH "SEE ALSO"

View File

@ -85,7 +85,7 @@ or
.BR lseek (2).
.SH "CONFORMING TO"
POSIX.1-2001.
.SH HISTORY
.SH VERSIONS
The
.BR pread ()
and

View File

@ -101,7 +101,7 @@ A component of the path prefix is not a directory.
.BR readlink ()
function call appeared in 4.2BSD),
POSIX.1-2001.
.SH HISTORY
.SH NOTES
In versions of glibc up to and including glibc 2.4, the return type of
.BR readlink ()
was declared as

View File

@ -194,7 +194,7 @@ system call returns the size (in bytes) of the
.I cpumask_t
data type that is used internally by the kernel to
represent the CPU set bitmask.
.SH "HISTORY"
.SH VERSIONS
The CPU affinity system calls were introduced in Linux kernel 2.5.8.
The library interfaces were introduced in glibc 2.3.
Initially, the glibc interfaces included a

View File

@ -79,7 +79,7 @@ Errors are ignored.
.SH "RETURN VALUE"
.BR set_tid_address ()
returns the PID of the current process.
.SH HISTORY
.SH VERSIONS
This call is present since Linux 2.5.48.
Details as given here are valid since Linux 2.5.49.
.SH "CONFORMING TO"

View File

@ -79,10 +79,8 @@ capability) and tried to change the IDs to values that are not permitted.
.SH "CONFORMING TO"
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.
.SH VERSIONS
It is available under Linux since Linux 2.1.44.
These days it is also found in FreeBSD (for emulation of Linux binaries).
.SH NOTES
Under HP-UX and FreeBSD the prototype is found in
.IR <unistd.h> .

View File

@ -130,15 +130,7 @@ The specified size of the new alternate signal stack
An attempt was made to change the alternate signal stack while
it was active (i.e., the process was already executing
on the current alternate signal stack).
.SH NOTES
The most common usage of an alternate signal stack is to handle the
.B SIGSEGV
signal that is generated if the space available for the
normal process stack is exhausted: in this case, a signal handler for
.B SIGSEGV
cannot be invoked on the process stack; if we wish to handle it,
we must use an alternate signal stack.
.SH EXAMPLE
The following code segment demonstrates the use of
.BR sigaltstack ():
@ -155,6 +147,14 @@ if (sigaltstack(&ss, NULL) == \-1)
/* Handle error */;
.fi
.RE
.SH NOTES
The most common usage of an alternate signal stack is to handle the
.B SIGSEGV
signal that is generated if the space available for the
normal process stack is exhausted: in this case, a signal handler for
.B SIGSEGV
cannot be invoked on the process stack; if we wish to handle it,
we must use an alternate signal stack.
.P
Establishing an alternate signal stack is useful if a process
expects that it may exhaust its standard stack.
@ -194,7 +194,7 @@ For backwards compatibility, glibc also provides
.BR sigstack ().
All new applications should be written using
.BR sigaltstack ().
.SH HISTORY
.SS History
4.2BSD had a
.BR sigstack ()
system call.

View File

@ -140,22 +140,6 @@ are allowed and input attempts result in an end-of-file indication."
.\" cannot follow
.\" .BR vfork ()
.\" and requires a kernel patch.
.SH HISTORY
The
.BR vfork ()
system call appeared in 3.0BSD.
.\" In the release notes for 4.2BSD Sam Leffler wrote: `vfork: Is still
.\" present, but definitely on its way out'.
In 4.4BSD it was made synonymous to
.BR fork (2)
but NetBSD introduced it again,
cf. http://www.netbsd.org/Documentation/kernel/vfork.html .
In Linux, it has been equivalent to
.BR fork (2)
until 2.2.0-pre6 or so.
Since 2.2.0-pre9 (on i386, somewhat later on
other architectures) it is an independent system call.
Support was added in glibc 2.0.112.
.SH "CONFORMING TO"
4.3BSD, POSIX.1-2001.
.\" FIXME Mar 07: in the draft of the next POSIX revision, the spec for
@ -184,6 +168,22 @@ LinuxThreads threading library.
(See
.BR pthreads (7)
for a description of Linux threading libraries.)
.SS History
The
.BR vfork ()
system call appeared in 3.0BSD.
.\" In the release notes for 4.2BSD Sam Leffler wrote: `vfork: Is still
.\" present, but definitely on its way out'.
In 4.4BSD it was made synonymous to
.BR fork (2)
but NetBSD introduced it again,
cf. http://www.netbsd.org/Documentation/kernel/vfork.html .
In Linux, it has been equivalent to
.BR fork (2)
until 2.2.0-pre6 or so.
Since 2.2.0-pre9 (on i386, somewhat later on
other architectures) it is an independent system call.
Support was added in glibc 2.0.112.
.SH "SEE ALSO"
.BR clone (2),
.BR execve (2),

View File

@ -78,10 +78,10 @@ On a glibc system, these functions are declared by
when _BSD_SOURCE or _SVID_SOURCE or _GNU_SOURCE is defined.
The isnan() functions will also be declared when _XOPEN_SOURCE
is defined.
.SH HISTORY
The
.BR finite ()
function occurs in 4.3BSD.
.\" .SH HISTORY
.\" The
.\" .BR finite ()
.\" function occurs in 4.3BSD.
.\" see IEEE.3 in the 4.3BSD manual
.SH "SEE ALSO"
.BR fpclassify (3),

View File

@ -76,10 +76,10 @@ gives nanoseconds but is not yet widely available.
Under libc4 and libc5 the \fImillitm\fP field is meaningful.
But early glibc2 is buggy and returns 0 there;
glibc 2.1.1 is correct again.
.SH HISTORY
The
.BR ftime ()
function appeared in 4.2BSD.
.\" .SH HISTORY
.\" The
.\" .BR ftime ()
.\" function appeared in 4.2BSD.
.SH "CONFORMING TO"
4.2BSD, POSIX.1-2001.
.SH "SEE ALSO"

View File

@ -31,7 +31,8 @@ function that is equivalent to
and computes the natural logarithm of the Gamma function.
(This is for compatibility reasons only.
Don't use this function.)
.SH HISTORY
.SH NOTES
.SS History
4.2BSD had a
.BR gamma ()
that computed

View File

@ -99,10 +99,10 @@ return a pointer to a struct fstab, while
.BR setfsent ()
returns 1.
Upon failure or end-of-file, these functions return NULL and 0, respectively.
.SH HISTORY
The
.BR getfsent ()
function appeared in 4.0BSD; the other four functions appeared in 4.3BSD.
.\" .SH HISTORY
.\" The
.\" .BR getfsent ()
.\" function appeared in 4.0BSD; the other four functions appeared in 4.3BSD.
.SH "CONFORMING TO"
These functions are not in POSIX.1-2001.
Several operating systems have them,

View File

@ -94,10 +94,10 @@ Libc4 and libc5 have never supported PASS_MAX or _SC_PASS_MAX.
Glibc2 accepts _SC_PASS_MAX and returns BUFSIZ (e.g., 8192).
.SH FILES
.I /dev/tty
.SH HISTORY
A
.BR getpass ()
function appeared in Version 7 AT&T UNIX.
.\" .SH HISTORY
.\" A
.\" .BR getpass ()
.\" function appeared in Version 7 AT&T UNIX.
.SH "CONFORMING TO"
Present in SUSv2, but marked LEGACY.
Removed in POSIX.1-2001.

View File

@ -91,10 +91,10 @@ is non-zero, then the divide-by-zero floating-point exception is raised.
A pole error occurs when
.I x
is zero.
.SH HISTORY
The
.BR logb ()
function occurs in 4.3BSD.
.\" .SH HISTORY
.\" The
.\" .BR logb ()
.\" function occurs in 4.3BSD.
.\" see IEEE.3 in the 4.3BSD manual
.SH "CONFORMING TO"
C99

View File

@ -158,12 +158,12 @@ before
Failure to execute the shell is indistinguishable from the shell's failure
to execute command, or an immediate exit of the command.
The only hint is an exit status of 127.
.SH HISTORY
A
.BR popen ()
and a
.BR pclose ()
function appeared in Version 7 AT&T UNIX.
.\" .SH HISTORY
.\" A
.\" .BR popen ()
.\" and a
.\" .BR pclose ()
.\" function appeared in Version 7 AT&T UNIX.
.SH "SEE ALSO"
.BR sh (1),
.BR fork (2),

View File

@ -912,39 +912,39 @@ glibc 2.1 adds length modifiers hh,j,t,z and conversion characters a,A.
.PP
glibc 2.2 adds the conversion character F with C99 semantics, and the
flag character I.
.SH HISTORY
Unix V7 defines the three routines
.BR printf (),
.BR fprintf (),
.BR sprintf (),
and has the flag \-, the width or precision *, the length modifier l,
and the conversions doxfegcsu, and also D,O,U,X as synonyms for ld,lo,lu,lx.
This is still true for 2.9.1BSD, but 2.10BSD has the flags
#, + and <space> and no longer mentions D,O,U,X.
2.11BSD has
.BR vprintf (),
.BR vfprintf (),
.BR vsprintf (),
and warns not to use D,O,U,X.
4.3BSD Reno has the flag 0, the length modifiers h and L,
and the conversions n, p, E, G, X (with current meaning)
and deprecates D,O,U.
4.4BSD introduces the functions
.BR snprintf ()
and
.BR vsnprintf (),
and the length modifier q.
FreeBSD also has functions
.BR asprintf ()
and
.BR vasprintf (),
that allocate a buffer large enough for
.BR sprintf ().
In glibc there are functions
.BR dprintf ()
and
.BR vdprintf ()
that print to a file descriptor instead of a stream.
.\" .SH HISTORY
.\" Unix V7 defines the three routines
.\" .BR printf (),
.\" .BR fprintf (),
.\" .BR sprintf (),
.\" and has the flag \-, the width or precision *, the length modifier l,
.\" and the conversions doxfegcsu, and also D,O,U,X as synonyms for ld,lo,lu,lx.
.\" This is still true for 2.9.1BSD, but 2.10BSD has the flags
.\" #, + and <space> and no longer mentions D,O,U,X.
.\" 2.11BSD has
.\" .BR vprintf (),
.\" .BR vfprintf (),
.\" .BR vsprintf (),
.\" and warns not to use D,O,U,X.
.\" 4.3BSD Reno has the flag 0, the length modifiers h and L,
.\" and the conversions n, p, E, G, X (with current meaning)
.\" and deprecates D,O,U.
.\" 4.4BSD introduces the functions
.\" .BR snprintf ()
.\" and
.\" .BR vsnprintf (),
.\" and the length modifier q.
.\" FreeBSD also has functions
.\" .BR asprintf ()
.\" and
.\" .BR vasprintf (),
.\" that allocate a buffer large enough for
.\" .BR sprintf ().
.\" In glibc there are functions
.\" .BR dprintf ()
.\" and
.\" .BR vdprintf ()
.\" that print to a file descriptor instead of a stream.
.SH BUGS
Because
.BR sprintf ()

View File

@ -138,11 +138,12 @@ may return \-1 to signify that PATH_MAX is not bounded.
The libc4 and libc5 implementation contains a buffer overflow
(fixed in libc-5.4.13).
Thus, set-user-ID programs like mount need a private version.
.SH HISTORY
The
.BR realpath ()
function first appeared in 4.4BSD, contributed by Jan-Simon Pendry.
In Linux this function appears in libc 4.5.21.
.\" .SH HISTORY
.\" The
.\" .BR realpath ()
.\" function first appeared in 4.4BSD, contributed by Jan-Simon Pendry.
.SH VERSIONS
On Linux this function appeared in libc 4.5.21.
.SH "CONFORMING TO"
4.4BSD, POSIX.1-2001.

View File

@ -29,8 +29,8 @@ scalb(x, (double) \-ilogb(x))
.PP
This function exists mainly for use in certain standardized tests
for IEEE 754 conformance.
.SH HISTORY
This function came from BSD.
.\" .SH HISTORY
.\" This function came from BSD.
.SH "SEE ALSO"
.BR ilogb (3),
.BR scalb (3)

View File

@ -51,7 +51,8 @@ with
.I errno
set to
.BR EINTR .
.SH HISTORY
.SH NOTES
.SS History
The classical BSD version of this function appeared in 4.2BSD.
It sets the process's signal mask to
.IR sigmask .
@ -72,7 +73,7 @@ On Linux, this routine is a system call only on the Sparc (sparc64)
architecture.
Libc4 and libc5 only know about the BSD version.
Glibc uses the BSD version unless _XOPEN_SOURCE is defined.
.\" .SH NOTES
.\"
.\" For the BSD version, one usually uses a zero
.\" .I sigmask
.\" to indicate that no signals are to be blocked.

View File

@ -260,22 +260,22 @@ value for
.I option
is not specified by POSIX.1-2001, but is available
in most versions of Unix.
.SH HISTORY
A
.BR syslog ()
function call appeared in 4.2BSD.
4.3BSD documents
.BR openlog (),
.BR syslog (),
.BR closelog (),
and
.BR setlogmask ().
4.3BSD-Reno also documents
.BR vsyslog ().
Of course early v* functions used the
.I <varargs.h>
mechanism, which is not compatible with
.IR <stdarg.h> .
.\" .SH HISTORY
.\" A
.\" .BR syslog ()
.\" function call appeared in 4.2BSD.
.\" 4.3BSD documents
.\" .BR openlog (),
.\" .BR syslog (),
.\" .BR closelog (),
.\" and
.\" .BR setlogmask ().
.\" 4.3BSD-Reno also documents
.\" .BR vsyslog ().
.\" Of course early v* functions used the
.\" .I <varargs.h>
.\" mechanism, which is not compatible with
.\" .IR <stdarg.h> .
.SH NOTES
The parameter
.I ident

View File

@ -101,8 +101,8 @@ process in the same session as the calling process.
.SH NOTES
These functions are implemented via the TIOCGPGRP and
TIOCSPGRP ioctls.
.SH HISTORY
These ioctls appeared in 4.2BSD.
.SS History
The ioctls appeared in 4.2BSD.
The functions are POSIX inventions.
.SH "CONFORMING TO"
POSIX.1-2001.

View File

@ -121,9 +121,9 @@ always return 0.
.LP
Minix also has
.IR fttyslot ( fd ).
.SH HISTORY
.BR ttyslot ()
appeared in Unix V7.
.\" .SH HISTORY
.\" .BR ttyslot ()
.\" appeared in Unix V7.
.SH "CONFORMING TO"
SUSv1; marked as LECACY in SUSv2; removed in POSIX.1-2001.
SUSv2 requires \-1 on error.

View File

@ -110,7 +110,7 @@ main(void)
/dev/vcsa[0\-63]
.SH AUTHOR
Andries Brouwer <aeb@cwi.nl>
.SH HISTORY
.SH VERSIONS
Introduced with version 1.1.92 of the Linux kernel.
.SH "SEE ALSO"
.BR gpm (8),

View File

@ -122,7 +122,8 @@ _
.in
.ft P
\}
.SH HISTORY
.SH NOTES
.SS History
An
.B ascii
manual page appeared in Version 7 of AT&T UNIX.

View File

@ -152,7 +152,7 @@ _
375 253 FD ý GREEK SMALL LETTER UPSILON WITH TONOS
376 254 FE þ GREEK SMALL LETTER OMEGA WITH TONOS
.TE
.SH HISTORY
.SH NOTES
ISO 8859-7 was formerly known as ELOT-928 or ECMA-118:1986.
.SH "SEE ALSO"
.BR ascii (7)

View File

@ -339,6 +339,19 @@ In addition other errors may be generated by the low-level driver.
is a new feature in Linux 2.2.
Earlier Linux versions supported only
.BR SOCK_PACKET .
.PP
The include file
.I <netpacket/packet.h>
is present since glibc 2.1.
Older systems need:
.sp
.in +0.5i
.nf
#include <asm/types.h>
#include <linux/if_packet.h>
#include <linux/if_ether.h> /* The L2 protocols */
.fi
.in
.SH BUGS
glibc 2.1 does not have a define for
.BR SOL_PACKET .
@ -365,20 +378,6 @@ The
extension is an ugly hack and should be replaced by a control message.
There is currently no way to get the original destination address of
packets via SOCK_DGRAM.
.SH HISTORICAL NOTE
The include file
.I <netpacket/packet.h>
is present since glibc 2.1.
Older systems need
.sp
.nf
.B #include <asm/types.h>
.br
.B #include <linux/if_packet.h>
.br
.B #include <linux/if_ether.h> /* The L2 protocols */
.br
.fi
.\" .SH CREDITS
.\" This man page was written by Andi Kleen with help from Matthew Wilcox.
.\" PF_PACKET in Linux 2.2 was implemented