mirror of https://github.com/mkerrisk/man-pages
Replace "SYSV" by "System V"
This commit is contained in:
parent
aa651b3950
commit
80b50848d0
2
Changes
2
Changes
|
@ -80,7 +80,7 @@ unix.7
|
|||
|
||||
Various pages
|
||||
mtk
|
||||
Replace "SysV" by "System V".
|
||||
Replace "SysV"/"SYSV" by "System V".
|
||||
|
||||
Typographical or grammatical errors have been corrected in several
|
||||
places.
|
||||
|
|
|
@ -153,7 +153,7 @@ for details.
|
|||
.SH NOTES
|
||||
The details on the condition for EPERM depend on the system.
|
||||
The above description is what SUSv3 says, and seems to be followed on
|
||||
all SYSV-like systems.
|
||||
all System V-like systems.
|
||||
Linux kernels before 2.6.12 required 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).
|
||||
|
|
|
@ -94,7 +94,7 @@ The process group was given as 0 but the sending process does not
|
|||
have a process group.
|
||||
.SH NOTES
|
||||
There are various differences between the permission checking
|
||||
in BSD-type systems and SYSV-type systems. See the POSIX rationale
|
||||
in BSD-type systems and System V-type systems. See the POSIX rationale
|
||||
for
|
||||
.BR kill ().
|
||||
A difference not mentioned by POSIX concerns the return
|
||||
|
|
|
@ -103,7 +103,7 @@ does not support the creation of directories.
|
|||
.I pathname
|
||||
refers to a file on a read-only filesystem.
|
||||
.SH "CONFORMING TO"
|
||||
SVr4, POSIX, BSD, SYSV, X/OPEN. SVr4 documents additional EIO, EMULTIHOP
|
||||
SVr4, POSIX, BSD, X/OPEN. SVr4 documents additional EIO, EMULTIHOP
|
||||
and ENOLINK error conditions; POSIX.1 omits ELOOP.
|
||||
.SH NOTES
|
||||
Under Linux apart from the permission bits, only the S_ISVTX mode bit
|
||||
|
|
|
@ -57,7 +57,7 @@ herror, hstrerror \- get network host entry
|
|||
.sp
|
||||
.BI "const char *hstrerror(int " err );
|
||||
.sp 2
|
||||
/* SYSV/POSIX extension */
|
||||
/* System V/POSIX extension */
|
||||
.br
|
||||
.B struct hostent *gethostent(void);
|
||||
.sp 2
|
||||
|
@ -236,7 +236,7 @@ host database file
|
|||
name service switch configuration
|
||||
.SH "CONFORMING TO"
|
||||
4.3BSD.
|
||||
.SH "SYSV/POSIX EXTENSION"
|
||||
.SH "System V/POSIX EXTENSION"
|
||||
POSIX requires the
|
||||
.BR gethostent ()
|
||||
call, that should return the next entry in the host data base.
|
||||
|
|
|
@ -75,7 +75,7 @@ Insufficient memory to allocate passwd structure.
|
|||
.I /etc/passwd
|
||||
password database file
|
||||
.SH "CONFORMING TO"
|
||||
SYSVr2.
|
||||
SVr2.
|
||||
.SH BUGS
|
||||
The
|
||||
.BR getpw ()
|
||||
|
|
|
@ -43,7 +43,7 @@ and
|
|||
.BR signal (),
|
||||
respectively.
|
||||
.LP
|
||||
Elsewhere, on SYSV-like systems, these functions implement
|
||||
Elsewhere, on System V-like systems, these functions implement
|
||||
software signalling, entirely independent of the classical
|
||||
signal and kill functions. The function
|
||||
.BR ssignal ()
|
||||
|
|
|
@ -115,7 +115,7 @@ An invalid operation was specified in
|
|||
.B ENOLCK
|
||||
Too many segment locks open, lock table is full.
|
||||
.SH "CONFORMING TO"
|
||||
SYSV, POSIX 1003.1-2001
|
||||
System V, POSIX 1003.1-2001
|
||||
.SH "SEE ALSO"
|
||||
.BR fcntl (2),
|
||||
.BR flock (2)
|
||||
|
|
|
@ -52,7 +52,7 @@ non-zero when returning from \fBlongjmp\fP() using the saved context.
|
|||
POSIX, ISO 9899 (C99)
|
||||
.SH NOTES
|
||||
POSIX does not specify whether \fBsetjmp\fP() will save the
|
||||
signal context. (In SYSV it will not. In 4.3BSD will, and there
|
||||
signal context. (In System V it will not. In 4.3BSD it will, and there
|
||||
is a function \fB_setjmp\fP that will not.)
|
||||
If you want to save signal masks, use \fBsigsetjmp\fP().
|
||||
.P
|
||||
|
|
|
@ -30,7 +30,7 @@ ttyslot \- find the slot of the current user's terminal in some file
|
|||
.sp
|
||||
.BR "#include <unistd.h>" " /* on BSD-like systems */"
|
||||
.br
|
||||
.BR "#include <stdlib.h>" " /* on SYSV-like systems */"
|
||||
.BR "#include <stdlib.h>" " /* on System V-like systems */"
|
||||
.sp
|
||||
.B "int ttyslot(void);"
|
||||
.SH DESCRIPTION
|
||||
|
@ -64,7 +64,7 @@ while the rest of the line contained the name of the tty.
|
|||
Thus a typical line was "14console".
|
||||
.LP
|
||||
Later systems have more elaborate syntax.
|
||||
SYSV-like systems have
|
||||
System V-like systems have
|
||||
.I /etc/inittab
|
||||
instead.
|
||||
.SS "Ancient History (2)"
|
||||
|
@ -91,7 +91,7 @@ current user in the file
|
|||
.IR /etc/utmp .
|
||||
BSD still has the
|
||||
.I /etc/ttys
|
||||
file, but SYSV-like systems do not, and hence cannot refer to it.
|
||||
file, but System V-like systems do not, and hence cannot refer to it.
|
||||
Thus, on such systems the documentation says that
|
||||
.BR ttyslot ()
|
||||
returns the current user's index in the user accounting data base.
|
||||
|
@ -100,7 +100,7 @@ If successful, this function returns the slot number.
|
|||
On error (e.g., if none of the file descriptors 0, 1 or 2 is
|
||||
associated with a terminal that occurs in this data base)
|
||||
it returns 0 on Unix V6 and V7 and BSD-like systems,
|
||||
but \-1 on SYSV-like systems.
|
||||
but \-1 on System V-like systems.
|
||||
.SH NOTES
|
||||
The utmp file is found various places on various systems, such as
|
||||
.IR /etc/utmp ,
|
||||
|
|
|
@ -486,7 +486,7 @@ drives that only support the logical block addresses.
|
|||
When this option is enabled, the tape devices use the SystemV
|
||||
semantics. Otherwise the BSD semantics are used. The most important
|
||||
difference between the semantics is what happens when a device used
|
||||
for reading is closed: in SYSV semantics the tape is spaced forward
|
||||
for reading is closed: in System V semantics the tape is spaced forward
|
||||
past the next filemark if this has not happened while using the
|
||||
device. In BSD semantics the tape position is not changed.
|
||||
.IP "\s-1MT_NO_WAIT\s+1 (Default: false)"
|
||||
|
|
10
man5/utmp.5
10
man5/utmp.5
|
@ -226,24 +226,24 @@ ut.ut_tv.tv_usec = tv.tv_usec;
|
|||
.br
|
||||
/var/log/wtmp
|
||||
.SH "CONFORMING TO"
|
||||
Linux utmp entries conform neither to v7/BSD nor to SYSV; they are a
|
||||
Linux utmp entries conform neither to v7/BSD nor to System V; they are a
|
||||
mix of the two. v7/BSD has fewer fields; most importantly it lacks
|
||||
\fIut_type\fP, which causes native v7/BSD-like programs to display (for
|
||||
example) dead or login entries. Further, there is no configuration file
|
||||
which allocates slots to sessions. BSD does so because it lacks
|
||||
\fIut_id\fP fields. In Linux (as in SYSV), the \fIut_id\fP field of a
|
||||
\fIut_id\fP fields. In Linux (as in System V), the \fIut_id\fP field of a
|
||||
record will never change once it has been set, which reserves that slot
|
||||
without needing a configuration file. Clearing \fIut_id\fP may result
|
||||
in race conditions leading to corrupted utmp entries and potential
|
||||
security holes. Clearing the above mentioned fields by filling them
|
||||
with null bytes is not required by SYSV semantics, but it allows to run
|
||||
with null bytes is not required by System V semantics, but it allows to run
|
||||
many programs which assume BSD semantics and which do not modify utmp.
|
||||
Linux uses the BSD conventions for line contents, as documented above.
|
||||
.PP
|
||||
SYSV only uses the type field to mark them and logs informative messages
|
||||
System V only uses the type field to mark them and logs informative messages
|
||||
such as e.g.\& \fB"new time"\fP in the line field. \fBUT_UNKNOWN\fP seems
|
||||
to be a Linux invention.
|
||||
SYSV has no \fIut_host\fP or \fIut_addr_v6\fP fields.
|
||||
System V has no \fIut_host\fP or \fIut_addr_v6\fP fields.
|
||||
.PP
|
||||
Unlike various other
|
||||
systems, where utmp logging can be disabled by removing the file, utmp
|
||||
|
|
|
@ -125,7 +125,7 @@ that actually start/stop the individual services.
|
|||
|
||||
.TP
|
||||
Note:
|
||||
The following description applies to SYSV\-R4 based system, which
|
||||
The following description applies to System V release 4 based system, which
|
||||
currently covers most commercial Unices (Solaris, HPUX, Irix, Tru64)
|
||||
as well as the major Linux distributions (RedHat, Debian, Mandrake,
|
||||
Suse, Caldera). Some systems (Slackware Linux, FreeBSD, OpenBSD)
|
||||
|
|
Loading…
Reference in New Issue