LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

s/Unices/Unix systems/

This commit is contained in:
Michael Kerrisk 2006-12-17 01:04:18 +00:00
parent d14e88c30e
commit d24e23199c
5 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man2/flock.2
View File

@ -139,7 +139,7 @@ A version of
.BR flock (2),
possibly implemented in terms of
.BR fcntl (2),
appears on most Unices.
appears on most Unix systems.
.SH NOTES
.BR flock (2)
does not lock files over NFS. Use

2
man3/clock.3
View File

@ -22,7 +22,7 @@
.\" License.
.\" Modified Sat Jul 24 21:27:01 1993 by Rik Faith (faith@cs.unc.edu)
.\" Modified 14 Jun 2002, Michael Kerrisk <mtk-manpages@gmx.net>
.\" Added notes on differences from other Unices with respect to
.\" Added notes on differences from other Unix systems with respect to
.\" waited-for children.
.TH CLOCK 3 2002-06-14 "GNU" "Linux Programmer's Manual"
.SH NAME

2
man3/shm_open.3
View File

@ -236,7 +236,7 @@ POSIX leaves the behavior of the combination of
and
.B O_TRUNC
unspecified. On Linux, this will successfully truncate an existing
shared memory object \(em this may not be so on other Unices.
shared memory object \(em this may not be so on other Unix systems.
.LP
The POSIX shared memory object implementation on Linux 2.4 makes use
of a dedicated file system, which is normally

4
man7/boot.7
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, HP-UX, Irix, Tru64)
currently covers most commercial Unix systems (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.
@ -179,7 +179,7 @@ configuration files are used. These are located in a specific
directory (\fI/etc/sysconfig\fR on RedHat systems) and are
used by the boot scripts.
In older Unices, these files contained the actual command line
In older Unix systems, these files contained the actual command line
options for the daemons, but in modern Linux systems (and also
in HP-UX), these files just contain shell variables. The boot
scripts in \fI/etc/init.d\fR \fBsource\fR the configuration

11
man7/signal.7
View File

@ -177,7 +177,7 @@ Up to and including Linux 2.2, the default behaviour for
and (on architectures other than SPARC and MIPS)
.B SIGBUS
was to terminate the process (without a core dump).
(On some other Unices the default action for
(On some other Unix systems the default action for
.BR SIGXCPU " and " SIGXFSZ
is to terminate the process without a core dump.)
Linux 2.4 conforms to the POSIX.1-2001 requirements for these signals,
@ -211,16 +211,17 @@ on a sparc.)
.B SIGEMT
is not specified in POSIX.1-2001, but nevertheless appears
on most other Unices, where its default action is typically to terminate
on most other Unix systems,
where its default action is typically to terminate
the process with a core dump.
.B SIGPWR
(which is not specified in POSIX.1-2001) is typically ignored
by default on those other Unices where it appears.
by default on those other Unix systems where it appears.
.B SIGIO
(which is not specified in POSIX.1-2001) is ignored by default
on several other Unices.
on several other Unix systems.
.SS "Real-time Signals"
Linux supports real-time signals as originally defined in the POSIX.1b
real-time extensions (and now included in POSIX.1-2001).
@ -230,7 +231,7 @@ to 63
.RB ( SIGRTMAX ).
(Programs should always refer to real-time signals using notation
.BR SIGRTMIN +n,
since the range of real-time signal numbers varies across Unices.)
since the range of real-time signal numbers varies across Unix systems.)
.PP
Unlike standard signals, real-time signals have no predefined meanings:
the entire set of real-time signals can be used for application-defined