Updated CONFORMING TO section

This commit is contained in:
Michael Kerrisk 2006-08-03 13:58:08 +00:00
parent 72cedc067b
commit 4dec66f990
9 changed files with 30 additions and 29 deletions

View File

@ -126,7 +126,7 @@ that actually start/stop the individual services.
.TP
Note:
The following description applies to System V release 4 based system, which
currently covers most commercial Unices (Solaris, HPUX, Irix, Tru64)
currently covers most commercial Unices (Solaris, HP-UX, Irix, Tru64)
as well as the major Linux distributions (RedHat, Debian, Mandrake,
Suse, Caldera). Some systems (Slackware Linux, FreeBSD, OpenBSD)
have a somewhat different scheme of boot scripts.
@ -181,7 +181,7 @@ used by the boot scripts.
In older Unices, these files contained the actual command line
options for the daemons, but in modern Linux systems (and also
in HPUX), these files just contain shell variables. The boot
in HP-UX), these files just contain shell variables. The boot
scripts in \fI/etc/init.d\fR \fBsource\fR the configuration
files, and then use the variable values.
.SH "FILES"

View File

@ -519,7 +519,7 @@ and
.BR capget (2).
.SH "CONFORMING TO"
No standards govern capabilities, but the Linux capability implementation
is based on the withdrawn POSIX 1003.1e draft standard.
is based on the withdrawn POSIX.1e draft standard.
.SH BUGS
There is as yet no file system support allowing capabilities to be
associated with executable files.

View File

@ -106,7 +106,8 @@ some situations where standards conflict.
.B _SVID_SOURCE
Defining this macro with any value cause header files to expose
System V-derived definitions.
(SVID == System V Interface Definition.)
(SVID == System V Interface Definition; see
.BR standards (7).)
.TP
.B _GNU_SOURCE
Defining this macro (with any value) is equivalent to defining

View File

@ -35,7 +35,7 @@ These days there is also a library routine
.BR glob (3)
that will perform this function for a user program.
The rules are as follows (POSIX 1003.2, 3.13).
The rules are as follows (POSIX.2, 3.13).
.SH "WILDCARD MATCHING"
A string is a wildcard pattern if it contains one of the
characters `?', `*' or `['. Globbing is the operation

View File

@ -24,7 +24,7 @@
.SH NAME
posixoptions \- optional parts of the POSIX standard
.SH DESCRIPTION
The POSIX standard (the information below is from POSIX 1003.1-2001)
The POSIX standard (the information below is from POSIX.1-2001)
describes a set of behaviours and interfaces for a compliant system.
However, many interfaces are optional and there are feature test macros
to test the availability of interfaces at compile time, and functions
@ -97,7 +97,7 @@ are present.
.\" .SS "CD"
.\" C development.
.SS "--- - POSIX_CHOWN_RESTRICTED"
If this option is in effect (as it always is under POSIX 1003.1-2001)
If this option is in effect (as it always is under POSIX.1-2001)
then only root may change the owner of a file, and non-root can only
set the group of a file to one of the groups it belongs to.
This affects the functions
@ -140,7 +140,7 @@ is present.
.SS "IP6 - _POSIX_IPV6 - _SC_IPV6"
Internet Protocol Version 6 is supported.
.SS "--- - _POSIX_JOB_CONTROL - _SC_JOB_CONTROL"
If this option is in effect (as it always is under POSIX 1003.1-2001)
If this option is in effect (as it always is under POSIX.1-2001)
then the system implements POSIX-style job control, and the functions
.br
.nf
@ -214,7 +214,7 @@ This option has been deleted. Not in final XPG6.
.\" .SS "MX"
.\" IEC 60559 Floating-Point Option.
.SS "--- - _POSIX_NO_TRUNC"
If this option is in effect (as it always is under POSIX 1003.1-2001)
If this option is in effect (as it always is under POSIX.1-2001)
then pathname components longer than NAME_MAX are not truncated,
but give an error.
This property may be dependent on the path prefix of the component.
@ -264,7 +264,7 @@ Raw sockets are supported. Affected functions are
.IR setsockopt ().
.SS "--- - _POSIX_READER_WRITER_LOCKS - _SC_READER_WRITER_LOCKS"
This option implies the _POSIX_THREADS option. Conversely,
under POSIX 1003.1-2001 the _POSIX_THREADS option implies this option.
under POSIX.1-2001 the _POSIX_THREADS option implies this option.
.nf
The functions
.in +4
@ -293,7 +293,7 @@ Realtime signals are supported. The functions
.fi
are present.
.SS "--- - _POSIX_REGEXP - _SC_REGEXP"
If this option is in effect (as it always is under POSIX 1003.1-2001)
If this option is in effect (as it always is under POSIX.1-2001)
then POSIX regular expressions are supported and the functions
.br
.nf
@ -307,7 +307,7 @@ then POSIX regular expressions are supported and the functions
.fi
are present.
.SS "--- - _POSIX_SAVED_IDS - _SC_SAVED_IDS"
If this option is in effect (as it always is under POSIX 1003.1-2001)
If this option is in effect (as it always is under POSIX.1-2001)
then a process has a saved set-user-ID and a saved set-group-ID.
Affected functions are
.br
@ -359,7 +359,7 @@ The functions
.fi
are present.
.SS "--- - _POSIX_SHELL - _SC_SHELL"
If this option is in effect (as it always is under POSIX 1003.1-2001),
If this option is in effect (as it always is under POSIX.1-2001),
the function
.IR system ()
is present.

View File

@ -34,10 +34,10 @@
.el .ds dg (!)
.TH REGEX 7 1994-02-07
.SH NAME
regex \- POSIX 1003.2 regular expressions
regex \- POSIX.2 regular expressions
.SH DESCRIPTION
Regular expressions (``RE''s),
as defined in POSIX 1003.2, come in two forms:
as defined in POSIX.2, come in two forms:
modern REs (roughly those of
.IR egrep ;
1003.2 calls these ``extended'' REs)
@ -177,7 +177,7 @@ A character class may not be used as an endpoint of a range.
.\" .BR wctype (3))
.\" or an underscore.
.\" This is an extension,
.\" compatible with but not specified by POSIX 1003.2,
.\" compatible with but not specified by POSIX.2,
.\" and should be used with
.\" caution in software intended to be portable to other systems.
.PP
@ -244,7 +244,7 @@ so that (e.g.) `\e([bc]\e)\e1' matches `bb' or `cc' but not `bc'.
.SH "SEE ALSO"
.BR regex (3)
.PP
POSIX 1003.2, section 2.8 (Regular Expression Notation).
POSIX.2, section 2.8 (Regular Expression Notation).
.SH BUGS
Having two kinds of REs is a botch.
.PP

View File

@ -120,7 +120,7 @@ alpha and sparc, the middle one for i386, ppc and sh, and
the last one for mips.
A \- denotes that a signal is absent on the corresponding architecture.)
First the signals described in the original POSIX.1 standard.
First the signals described in the original POSIX.1-1990 standard.
.TS
l c c l
____
@ -154,8 +154,8 @@ and
.B SIGSTOP
cannot be caught, blocked, or ignored.
Next the signals not in the POSIX.1 standard but described in SUSv2 and
SUSv3 / POSIX 1003.1-2001.
Next the signals not in the POSIX.1-1990 standard but described in
SUSv2 and POSIX.1-2001.
.TS
l c c l
____
@ -164,7 +164,7 @@ Signal Value Action Comment
SIGBUS 10,7,10 Core Bus error (bad memory access)
SIGPOLL Term Pollable event (Sys V). Synonym of SIGIO
SIGPROF 27,27,29 Term Profiling timer expired
SIGSYS 12,\-,12 Core Bad argument to routine (SVID)
SIGSYS 12,\-,12 Core Bad argument to routine (SVr4)
SIGTRAP 5 Core Trace/breakpoint trap
SIGURG 16,23,21 Ign Urgent condition on socket (4.2BSD)
SIGVTALRM 26,26,28 Term Virtual alarm clock (4.2BSD)
@ -180,7 +180,7 @@ was to terminate the process (without a core dump).
(On some other Unices the default action for
.BR SIGXCPU " and " SIGXFSZ
is to terminate the process without a core dump.)
Linux 2.4 conforms to the POSIX 1003.1-2001 requirements for these signals,
Linux 2.4 conforms to the POSIX.1-2001 requirements for these signals,
terminating the process with a core dump.
Next various other signals.
@ -210,20 +210,20 @@ on an alpha but
on a sparc.)
.B SIGEMT
is not specified in POSIX 1003.1-2001, but nevertheless appears
is not specified in POSIX.1-2001, but nevertheless appears
on most other Unices, where its default action is typically to terminate
the process with a core dump.
.B SIGPWR
(which is not specified in POSIX 1003.1-2001) is typically ignored
(which is not specified in POSIX.1-2001) is typically ignored
by default on those other Unices where it appears.
.B SIGIO
(which is not specified in POSIX 1003.1-2001) is ignored by default
(which is not specified in POSIX.1-2001) is ignored by default
on several other Unices.
.SS "Real-time Signals"
Linux supports real-time signals as originally defined in the POSIX.4
real-time extensions (and now included in POSIX 1003.1-2001).
Linux supports real-time signals as originally defined in the POSIX.1b
real-time extensions (and now included in POSIX.1-2001).
Linux supports 32 real-time signals, numbered from 32
.RB ( SIGRTMIN )
to 63

View File

@ -202,7 +202,7 @@ and read with
with the socket level set to
.B SOL_SOCKET
for all sockets:
.\" SO_ACCEPTCONN is in SUSv3, and its origin is explained in
.\" SO_ACCEPTCONN is in POSIX.1-2001, and its origin is explained in
.\" W R Stevens, UNPv1
.TP
.B SO_ACCEPTCONN

View File

@ -118,7 +118,7 @@ socket "owner" using the
.B SIOCSPGRP
or
.B FIOSETOWN
ioctls (or the SUSv3-specified
ioctls (or the POSIX.1-2001-specified
.BR fcntl (2)
.B F_SETOWN
operation).