use different nonzero status values to indicate the reason why the
command failed.
.SH NOTES
-Linux is a flavor of Unix, and as a first approximation
-all user commands under Unix work precisely the same under
-Linux (and FreeBSD and lots of other Unix-like systems).
+Linux is a flavor of UNIX, and as a first approximation
+all user commands under UNIX work precisely the same under
+Linux (and FreeBSD and lots of other UNIX-like systems).
.LP
Under Linux there are GUIs (graphical user interfaces), where you
can point and click and drag, and hopefully get work done without
first reading lots of documentation.
-The traditional Unix environment
+The traditional UNIX environment
is a CLI (command line interface), where you type commands to
tell the computer what to do.
That is faster and more powerful,
.I df
will tell you how much of your disk is still free.
.SS "Processes"
-On a Unix system many user and system processes run simultaneously.
+On a UNIX system many user and system processes run simultaneously.
The one you are talking to runs in the
.IR foreground ,
the others in the
.B "\-\-"
Terminate option list.
.SH BUGS
-Not all resources are measured by all versions of Unix,
+Not all resources are measured by all versions of UNIX,
so some of the values might be reported as zero.
The present selection was mostly inspired by the data
provided by 4.2 or 4.3BSD.
standard wanted to change it into a \fIsize_t *\fP, and that is what it is
for SunOS 5.
Later POSIX drafts have \fIsocklen_t *\fP,
-and so do the Single Unix Specification and glibc2.
+and so do the Single UNIX Specification and glibc2.
Quoting Linus Torvalds:
.\" .I fails: only italicizes a single line
.I sockfd
is a descriptor for a file, not a socket.
.PP
-The following errors are specific to Unix domain
+The following errors are specific to UNIX domain
.RB ( AF_UNIX )
sockets:
.TP
.\" .B EIO
.\" and
.\" .B EISDIR
-.\" Unix-domain error conditions.
+.\" UNIX-domain error conditions.
.SH NOTES
POSIX.1-2001 does not require the inclusion of
.IR <sys/types.h> ,
with Internet domain sockets can be found in
.BR getaddrinfo (3).
-The following example shows how to bind a stream socket in the Unix
+The following example shows how to bind a stream socket in the UNIX
.RB ( AF_UNIX )
domain, and accept connections:
.\" listen.7 refers to this example.
There may be other domain-specific error codes.
.TP
.B EACCES
-For Unix domain sockets, which are identified by pathname:
+For UNIX domain sockets, which are identified by pathname:
Write permission is denied on the socket file,
or search permission is denied for one of the directories
in the path prefix.
should either be absent, or be specified as a single word (i.e., it
should not contain white space); see NOTES below.
.SS "Limits on size of arguments and environment"
-Most Unix implementations impose some limit on the total size
+Most UNIX implementations impose some limit on the total size
of the command-line argument
.RI ( argv )
and environment
as a pointer to a list containing a single NULL pointer.
.B "Do not take advantage of this misfeature!"
It is nonstandard and nonportable:
-on most other Unix systems doing this will result in an error
+on most other UNIX systems doing this will result in an error
.RB ( EFAULT ).
.\" e.g., EFAULT on Solaris 8 and FreeBSD 6.1; but
.\" HP-UX 11 is like Linux -- mtk, Apr 2007
.\" that could be exploited for denial of service by a suitably crafted
.\" ELF binary. There are no known problems with 2.0.34 or 2.2.15.
.SS Historical
-With Unix V6 the argument list of an
+With UNIX V6 the argument list of an
.BR exec ()
call was ended by 0,
while the argument list of
Thus, this argument list was not directly usable in a further
.BR exec ()
call.
-Since Unix V7 both are NULL.
+Since UNIX V7 both are NULL.
.SH EXAMPLE
The following program is designed to be execed by the second program below.
It just echoes its command-line one per line.
.BR flock (),
possibly implemented in terms of
.BR fcntl (2),
-appears on most Unix systems.
+appears on most UNIX systems.
.SH NOTES
.BR flock ()
does not lock files over NFS.
This is a regular file.
.TP
.B DT_SOCK
-This is a Unix domain socket.
+This is a UNIX domain socket.
.TP
.B DT_UNKNOWN
The file type is unknown.
.BR execve (2).
The degree to which their relative nice value affects the scheduling of
-processes varies across Unix systems, and,
+processes varies across UNIX systems, and,
on Linux, across kernel versions.
Starting with kernel 2.6.23, Linux adopted an algorithm that causes
relative differences in nice values to have a much stronger effect.
POSIX.1-2001, 4.3BSD.
.SH NOTES
.SS History
-In Unix V6 the
+In UNIX V6 the
.BR getuid ()
call returned
.IR "(euid << 8) + uid" .
-Unix V7 introduced separate calls
+UNIX V7 introduced separate calls
.BR getuid ()
and
.BR geteuid ().
For further information on feature test macros, see
.BR feature_test_macros (7).
.SH "CONFORMING TO"
-Certain terms and abbreviations are used to indicate Unix variants
+Certain terms and abbreviations are used to indicate UNIX variants
and standards to which calls in this section conform.
See
.BR standards (7).
Arguments, returns, and semantics of
.BR ioctl ()
vary according to the device driver in question (the call is used as a
-catch-all for operations that don't cleanly fit the Unix stream I/O
+catch-all for operations that don't cleanly fit the UNIX stream I/O
model).
See
.BR ioctl_list (2)
calls.
The
.BR ioctl ()
-function call appeared in Version 7 AT&T Unix.
+function call appeared in Version 7 AT&T UNIX.
.SH NOTES
In order to use this call, one needs an open file descriptor.
Often the
.SH "CONFORMING TO"
.BR mincore ()
is not specified in POSIX.1-2001,
-and it is not available on all Unix implementations.
+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
.B S_IFSOCK
.\" (S_IFSOCK since Linux 1.2.4)
to specify a regular file (which will be created empty), character
-special file, block special file, FIFO (named pipe), or Unix domain socket,
+special file, block special file, FIFO (named pipe), or UNIX domain socket,
respectively.
(Zero file type is equivalent to type
.BR S_IFREG .)
.B EPERM
.I mode
requested creation of something other than a regular file,
-FIFO (named pipe), or Unix domain socket, and the caller
+FIFO (named pipe), or UNIX domain socket, and the caller
is not privileged (Linux: does not have the
.B CAP_MKNOD
capability);
-.\" For Unix domain sockets and regular files, EPERM is only returned in
+.\" For UNIX domain sockets and regular files, EPERM is only returned in
.\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
.\" use mknod() to make these files.
also returned if the file system containing
Under Linux, this call cannot be used to create directories.
One should make directories with
.BR mkdir (2).
-.\" and one should make Unix domain sockets with socket(2) and bind(2).
+.\" and one should make UNIX domain sockets with socket(2) and bind(2).
There are many infelicities in the protocol underlying NFS.
Some of these affect
signal numbers into signal actions.
The execution domain system allows
Linux to provide limited support for binaries compiled under other
-Unix-like operating systems.
+UNIX-like operating systems.
This function will return the current
.BR personality ()
This page documents the way the
.BR ptrace ()
call works currently in Linux.
-Its behavior differs noticeably on other flavors of Unix.
+Its behavior differs noticeably on other flavors of UNIX.
In any case, use of
.BR ptrace ()
is highly OS- and architecture-specific.
updates to the server and client side reads satisfied from the
client's cache will not cause st_atime updates on the server as there are no
server side reads.
-Unix semantics can be obtained by disabling client
+UNIX semantics can be obtained by disabling client
side attribute caching, but in most situations this will substantially
increase server load and decrease performance.
.PP
is NULL, nothing is filled in; in this case,
.I addrlen
is not used, and should also be NULL.
-.\" (Note: for datagram sockets in both the Unix and Internet domains,
+.\" (Note: for datagram sockets in both the UNIX and Internet domains,
.\" .I src_addr
.\" is filled in.
.\" .I src_addr
-.\" is also filled in for stream sockets in the Unix domain, but is not
+.\" is also filled in for stream sockets in the UNIX domain, but is not
.\" filled in for stream sockets in the Internet domain.)
.\" [The above notes on AF_UNIX and AF_INET sockets apply as at
.\" Kernel 2.4.18. (MTK, 22 Jul 02)]
.TP
.BR MSG_CMSG_CLOEXEC " (" recvmsg "() only; since Linux 2.6.23)"
Set the close-on-exec flag for the file descriptor received
-via a Unix domain file descriptor using the
+via a UNIX domain file descriptor using the
.B SCM_RIGHTS
operation (described in
.BR unix (7)).
and netlink (since Linux 2.6.22) sockets:
return the real length of the packet or datagram,
even when it was longer than the passed buffer.
-Not implemented for Unix domain
+Not implemented for UNIX domain
.RB ( unix (7))
sockets.
.BR cmsg (3).
.PP
As an example, Linux uses this ancillary data mechanism to pass extended
-errors, IP options, or file descriptors over Unix sockets.
+errors, IP options, or file descriptors over UNIX sockets.
.PP
The
.I msg_flags
flags.
.SH NOTES
The prototypes given above follow glibc2.
-The Single Unix Specification agrees, except that it has return values
+The Single UNIX Specification agrees, except that it has return values
of type \fIssize_t\fP (while 4.x BSD and libc4 and libc5 all have \fIint\fP).
The
.I flags
is that it watches
multiple descriptors at the same time and properly puts the process to
sleep if there is no activity.
-Unix programmers often find
+UNIX programmers often find
themselves in a position where they have to handle I/O from more than one
file descriptor where the data flow may be intermittent.
If you were to merely create a sequence of
select(0, NULL, NULL, NULL, &tv);
.fi
.PP
-This is only guaranteed to work on Unix systems, however.
+This is only guaranteed to work on UNIX systems, however.
.SH RETURN VALUE
On success,
.BR select ()
see their respective manual pages.
.TP
.B EACCES
-(For Unix domain sockets, which are identified by pathname)
+(For UNIX domain sockets, which are identified by pathname)
Write permission is denied on the destination socket file,
or search permission is denied for one of the directories
the path prefix.
.B MSG_CONFIRM
flag is a Linux extension.
.SH NOTES
-The prototypes given above follow the Single Unix Specification,
+The prototypes given above follow the Single UNIX Specification,
as glibc2 also does; the
.I flags
argument was \fIint\fP in 4.x BSD, but \fIunsigned int\fP in libc4 and libc5;
.SH "CONFORMING TO"
Not specified in POSIX.1-2001, or other standards.
-Other Unix systems implement
+Other UNIX systems implement
.BR sendfile ()
with different semantics and prototypes.
It should not be used in portable programs.
a shared memory segment that has already been marked for deletion
using
.IR shmctl(IPC_RMID) .
-This feature is not available on other Unix implementations;
+This feature is not available on other UNIX implementations;
portable applications should avoid relying on it.
Various fields in a \fIstruct shmid_ds\fP were typed as
Use of these latter values in
.I sa_flags
may be less portable in applications intended for older
-Unix implementations.
+UNIX implementations.
.PP
The
.B SA_RESETHAND
.SH DESCRIPTION
The behavior of
.BR signal ()
-varies across Unix versions,
+varies across UNIX versions,
and has also varied historically across different versions of Linux.
\fBAvoid its use\fP: use
.BR sigaction (2)
signal handler is invoked; use that interface instead of
.BR signal ().
-In the original Unix systems, when a handler that was established using
+In the original UNIX systems, when a handler that was established using
.BR signal ()
was invoked by the delivery of a signal,
the disposition of the signal would be reset to
POSIX.1-1996, but both are present in POSIX.1-2001;
the former is from SVID 4, the latter from SUSv2.
.LP
-Unix V7 (and later systems) had
+UNIX V7 (and later systems) had
.BR S_IREAD ,
.BR S_IWRITE ,
.BR S_IEXEC ,
.BR times ()
just returns a function result.
However, POSIX does not specify this behavior, and most
-other Unix implementations require a non-NULL value for
+other UNIX implementations require a non-NULL value for
.IR buf .
.LP
Note that
On Linux 2.4 and earlier this point is the moment the system was booted.
Since Linux 2.6, this point is \fI(2^32/HZ) \- 300\fP
(i.e., about 429 million) seconds before system boot time.
-This variability across kernel versions (and across Unix implementations),
+This variability across kernel versions (and across UNIX implementations),
combined with the fact that the returned value may overflow the range of
.IR clock_t ,
means that a portable application would be wise to avoid using this value.
.BR truncate ()
is not specified at all in such an environment):
either returning an error, or extending the file.
-Like most Unix implementations, Linux follows the XSI requirement
+Like most UNIX implementations, Linux follows the XSI requirement
when dealing with native file systems.
However, some nonnative file systems do not permit
.BR truncate ()
.BR shm_open (3)),
FIFOs
.RB ( mkfifo (3)),
-and Unix domain sockets
+and UNIX domain sockets
.RB ( unix (7))
created by the process.
The umask does not affect the permissions assigned
.B WIFSIGNALED
returned true.
This macro is not specified in POSIX.1-2001 and is not available on
-some Unix implementations (e.g., AIX, SunOS).
+some UNIX implementations (e.g., AIX, SunOS).
Only use this enclosed in #ifdef WCOREDUMP ... #endif.
.TP
.BI WIFSTOPPED( status )
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.\" Modified, aeb, 990824
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.\" Modified, aeb, 990824
.\"
.I str
into substrings separated by the delimiter
.IR delim .
-For example, one might use this on a Unix search path with
+For example, one might use this on a UNIX search path with
delimiter \(aq:\(aq.
.LP
.BR argz_append ()
.RI ( argz ,\ argz_len ).
.LP
.BR argz_create ()
-converts a Unix-style argument vector
+converts a UNIX-style argument vector
.IR argv ,
terminated by
.IR "(char *) 0" ,
and fills the array starting at
.I argv
with pointers to the substrings, and a final NULL,
-making a Unix-style argv vector.
+making a UNIX-style argv vector.
The array
.I argv
must have room for
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH BTOWC 3 2009-02-04 "GNU" "Linux Programmer's Manual"
.BR clearenv ()
function returns zero on success, and a nonzero
value on failure.
-.\" Most versions of Unix return -1 on error, or do not even have errors.
+.\" Most versions of UNIX return -1 on error, or do not even have errors.
.\" Glibc info and the Watcom C library document "a nonzero value".
.SH VERSIONS
Not in libc4, libc5.
In glibc since glibc 2.0.
.SH "CONFORMING TO"
-Various Unix variants (DG/UX, HP-UX, QNX, ...).
+Various UNIX variants (DG/UX, HP-UX, QNX, ...).
POSIX.9 (bindings for FORTRAN77).
POSIX.1-1996 did not accept
.BR clearenv ()
.\" License.
.\" Modified Sat Jul 24 21:27:01 1993 by Rik Faith (faith@cs.unc.edu)
.\" Modified 14 Jun 2002, Michael Kerrisk <mtk.manpages@gmail.com>
-.\" Added notes on differences from other Unix systems with respect to
+.\" Added notes on differences from other UNIX systems with respect to
.\" waited-for children.
.TH CLOCK 3 2008-08-28 "GNU" "Linux Programmer's Manual"
.SH NAME
ancillary data) that are not a part of the socket payload.
This control information may
include the interface the packet was received on, various rarely used header
-fields, an extended error description, a set of file descriptors or Unix
+fields, an extended error description, a set of file descriptors or UNIX
credentials.
For instance, control messages can be used to send
additional header fields such as IP options.
.fi
.in
.PP
-The code below passes an array of file descriptors over a Unix socket using
+The code below passes an array of file descriptors over a UNIX socket using
.BR SCM_RIGHTS :
.PP
.in +4n
This is the first address past the end of the
uninitialized data segment (also known as the BSS segment).
.SH CONFORMING TO
-Although these symbols have long been provided on most Unix systems,
+Although these symbols have long been provided on most UNIX systems,
they are not standardized; use with caution.
.SH NOTES
The program must explicitly declare these symbols;
The advantage of the
.BR byteorder (3)
functions is that they are standard functions available
-on all Unix systems.
+on all UNIX systems.
On the other hand, the fact that they were designed
for use in the context of TCP/IP means that
they lack the 64-bit and little-endian variants described in this page.
.IR <errno.h> .
.BR "Do not do this" .
It will not work with modern versions of the C library.
-However, on (very) old Unix systems, there may be no
+However, on (very) old UNIX systems, there may be no
.I <errno.h>
and the declaration is needed.
.SH "SEE ALSO"
and
.B EXIT_FAILURE
is slightly more portable
-(to non-Unix environments) than the use of 0 and some nonzero value
+(to non-UNIX environments) than the use of 0 and some nonzero value
like 1 or \-1.
In particular, VMS uses a different convention.
.LP
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
conforming systems, including Linux.
(Other systems may treat text files and binary files differently,
and adding the \(aqb\(aq may be a good idea if you do I/O to a binary
-file and expect that your program may be ported to non-Unix
+file and expect that your program may be ported to non-UNIX
environments.)
.PP
See NOTES below for details of glibc extensions for
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH FPUTWC 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH FPUTWS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
setting and storing the current value of the file offset into or from the
object referenced by
.IR pos .
-On some non-Unix systems an
+On some non-UNIX systems an
.I fpos_t
object may be a complex object and these routines may be the only way to
portably reposition a text stream.
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH FWIDE 3 2010-09-20 "GNU" "Linux Programmer's Manual"
.SH "CONFORMING TO"
These functions are not in POSIX.1-2001.
Several operating systems have them,
-e.g., *BSD, SunOS, Digital Unix, AIX (which also has a
+e.g., *BSD, SunOS, Digital UNIX, AIX (which also has a
.BR getfstype ()).
HP-UX has functions of the same names,
that however use a \fIstruct checklist\fP
.I errno
should be left unchanged if an entry is not found.
Experiments on various
-Unix-like systems shows that lots of different values occur in this
+UNIX-like systems shows that lots of different values occur in this
situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM and probably others.
.\" more precisely:
.\" AIX 5.1 - gives ESRCH
and
.BR sethostid ()
respectively get or set a unique 32-bit identifier for the current machine.
-The 32-bit identifier is intended to be unique among all Unix systems in
+The 32-bit identifier is intended to be unique among all UNIX systems in
existence.
This normally resembles the Internet address for the local
machine, as returned by
.SH NOTES
These functions were present in glibc 2.1.91-95, but were
removed again.
-Several Unix-like systems support them, but all
+Several UNIX-like systems support them, but all
call them deprecated.
.SH "SEE ALSO"
.BR getaddrinfo (3),
Under System V
.I /etc/mnttab
is used.
-4.4BSD and Digital Unix have a routine
+4.4BSD and Digital UNIX have a routine
.BR getmntinfo (),
a wrapper around the system call
.BR getfsstat ().
.I errno
should be left unchanged if an entry is not found.
Experiments on various
-Unix-like systems show that lots of different values occur in this
+UNIX-like systems show that lots of different values occur in this
situation: 0, ENOENT, EBADF, ESRCH, EWOULDBLOCK, EPERM and probably others.
.\" more precisely:
.\" AIX 5.1 - gives ESRCH
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.SH "CONFORMING TO"
POSIX.1-2001.
.SH NOTES
-This is part of the Unix98 pty support, see
+This is part of the UNIX 98 pty support, see
.BR pts (4).
Many systems implement this function via a set-user-ID helper binary
called "pt_chown".
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\"
.\" 2000-06-30 correction by Yuichi SATO <sato@complex.eng.hokudai.ac.jp>
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH ICONV_CLOSE 3 2008-08-11 "GNU" "Linux Programmer's Manual"
.SH NAME
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\"
.\" 2007-03-31 Bruno Haible, Describe the glibc/libiconv //TRANSLIT
including \fI<search.h>\fP.
The location of the prototypes for these functions differs among several
-versions of Unix.
+versions of UNIX.
The above is the POSIX version.
Some systems place them in \fI<string.h>\fP.
Linux libc4 and libc 5 placed them
.\" Various special libraries. The manual pages documenting their functions
.\" specify the library names.
.SH "CONFORMING TO"
-Certain terms and abbreviations are used to indicate Unix variants
+Certain terms and abbreviations are used to indicate UNIX variants
and standards to which calls in this section conform.
See
.BR standards (7).
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWALNUM 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWALPHA 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWBLANK 3 2010-09-20 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWCNTRL 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWCTYPE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWDIGIT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWGRAPH 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWLOWER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWPRINT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWPUNCT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWSPACE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWUPPER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH ISWXDIGIT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
resource limit (see
.BR getrlimit (2)).
-The Unix98 standard requires
+The UNIX 98 standard requires
.BR malloc (),
.BR calloc (),
and
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBLEN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
If \fIs\fP is a NULL pointer, the
.BR mblen ()
function
-.\" The Dinkumware doc and the Single Unix specification say this, but
+.\" The Dinkumware doc and the Single UNIX specification say this, but
.\" glibc doesn't implement this.
resets the shift state, only known to this function, to the initial state, and
returns nonzero if the encoding has nontrivial shift state, or zero if the
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBRLEN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBSINIT 3 2000-11-20 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH MBSNRTOWCS 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBSRTOWCS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBSTOWCS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH MBTOWC 3 2001-07-04 "GNU" "Linux Programmer's Manual"
The
.BR mbtowc ()
function
-.\" The Dinkumware doc and the Single Unix specification say this, but
+.\" The Dinkumware doc and the Single UNIX specification say this, but
.\" glibc doesn't implement this.
resets the shift state, only known to this function,
to the initial state, and
are glibc extensions.
.SH NOTES
The old behavior of creating a file with mode 0666 may be
-a security risk, especially since other Unix flavors use 0600,
+a security risk, especially since other UNIX flavors use 0600,
and somebody might overlook this detail when porting programs.
More generally, the POSIX specification of
.SH NOTES
The prototype is in
.I <unistd.h>
-for libc4, libc5, glibc1; glibc2 follows the Single Unix Specification
+for libc4, libc5, glibc1; glibc2 follows the Single UNIX Specification
and has the prototype in
.IR <stdlib.h> .
.SH BUGS
.\"
.\" References consulted:
.\" GNU glibc-2 manual
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.\" Corrected prototype, 2002-10-18, aeb
.\"
.BR openpty ()
returns file descriptors for a BSD pseudo-terminal pair;
since glibc 2.0.92,
-it first attempts to open a Unix 98 pseudo-terminal pair,
+it first attempts to open a UNIX 98 pseudo-terminal pair,
and falls back to opening a BSD pseudo-terminal pair if that fails.
.SH BUGS
Nobody knows how much space should be reserved for
has been provided since version 2.2.1.
.SH "CONFORMING TO"
.BR posix_openpt ()
-is part of the Unix98 pseudo-terminal support (see
+is part of the UNIX 98 pseudo-terminal support (see
.BR pts (4)).
This function is specified in POSIX.1-2001.
.SH NOTES
This function is a recent invention in POSIX.
-Some Unix implementations that support System V
-(aka Unix 98) pseudo-terminals don't have this function, but it
+Some UNIX implementations that support System V
+(aka UNIX 98) pseudo-terminals don't have this function, but it
is easy to implement:
.in +4n
.nf
The second style allows repeated references to the
same argument.
The C99 standard does not include the style using \(aq$\(aq,
-which comes from the Single Unix Specification.
+which comes from the Single UNIX Specification.
If the style using
\(aq$\(aq is used, it must be used throughout for all conversions taking an
argument and all width and precision arguments, but it may be mixed
Until glibc 2.0.6 they would return \-1
when the output was truncated.
.\" .SH HISTORY
-.\" Unix V7 defines the three routines
+.\" UNIX V7 defines the three routines
.\" .BR printf (),
.\" .BR fprintf (),
.\" .BR sprintf (),
is provided in glibc since version 2.1.
.SH "CONFORMING TO"
.BR ptsname ()
-is part of the Unix98 pseudo-terminal support (see
+is part of the UNIX 98 pseudo-terminal support (see
.BR pts (4)).
This function is specified in POSIX.1-2001.
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification
+.\" OpenGroup's Single UNIX specification
.\" http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.BR gcvt (3).
.SH "CONFORMING TO"
SVr4.
-Not seen in most common Unix implementations,
+Not seen in most common UNIX implementations,
but occurs in SunOS.
Not supported by libc4 and libc5.
Supported by glibc.
.IR *fd2p .
The control process will return diagnostic
output from the command (unit 2) on this channel, and will also
-accept bytes on this channel as being Unix signal numbers, to be
+accept bytes on this channel as being UNIX signal numbers, to be
forwarded to the process group of the command.
If
.I fd2p
This is a regular file.
.TP
.B DT_SOCK
-This is a Unix domain socket.
+This is a UNIX domain socket.
.TP
.B DT_UNKNOWN
The file type is unknown.
.IR *fd2p .
The control process will return diagnostic
output from the command (unit 2) on this channel, and will also
-accept bytes on this channel as being
-Unix
-signal numbers, to be
+accept bytes on this channel as being UNIX signal numbers, to be
forwarded to the process group of the command.
The diagnostic
information returned does not include remote authorization failure,
.BI "bool_t xdr_authunix_parms(XDR *" xdrs ", struct authunix_parms *" aupp );
.fi
.IP
-Used for describing Unix credentials.
+Used for describing UNIX credentials.
This routine is useful for users
who wish to generate these credentials without using the RPC
authentication package.
.BR getnetgrent (),
and
.BR innetgr ()
-are available on most Unix systems.
+are available on most UNIX systems.
.BR getnetgrent_r ()
is not widely available on other systems.
.\" getnetgrent_r() is on Solaris 8 and AIX 5.1, but not the BSDs.
.B O_TRUNC
unspecified.
On Linux, this will successfully truncate an existing
-shared memory object \(em this may not be so on other Unix systems.
+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
.sp
.BI "int sigpause(int " sigmask "); /* BSD */"
.sp
-.BI "int sigpause(int " sig "); /* System V / Unix95 */"
+.BI "int sigpause(int " sig "); /* System V / UNIX 95 */"
.fi
.SH DESCRIPTION
Don't use this function.
The classical BSD version of this function appeared in 4.2BSD.
It sets the process's signal mask to
.IR sigmask .
-Unix95 standardized the incompatible System V version of
+UNIX 95 standardized the incompatible System V version of
this function, which removes only the specified signal
.I sig
from the process's signal mask.
-.\" __xpg_sigpause: Unix 95, spec 1170, SVID, SVr4, XPG
+.\" __xpg_sigpause: UNIX 95, spec 1170, SVID, SVr4, XPG
The unfortunate situation with two incompatible functions with the
same name was solved by the
.BR \%sigsuspend (2)
.BI "extern FILE *" stderr ;
.fi
.SH DESCRIPTION
-Under normal circumstances every Unix program has three streams opened
+Under normal circumstances every UNIX program has three streams opened
for it when it starts up, one for input, one for output, and one for
printing diagnostic or error messages.
These are typically attached to
.PP
Since
.IR FILE s
-are a buffering wrapper around Unix file descriptors, the
-same underlying files may also be accessed using the raw Unix file
+are a buffering wrapper around UNIX file descriptors, the
+same underlying files may also be accessed using the raw UNIX file
interface, that is, the functions like
.BR read (2)
and
rather than the beginning.
.SH "CONFORMING TO"
This function is not part of the C or POSIX.1 standards, and is
-not customary on Unix systems, but is not a GNU invention either.
+not customary on UNIX systems, but is not a GNU invention either.
Perhaps it comes from MS-DOS.
Nowadays, it is also present on the BSDs.
.SH EXAMPLE
.\" Modified Sat Jul 24 18:03:44 1993 by Rik Faith (faith@cs.unc.edu)
.\" Applied fix by Wolfgang Franke, aeb, 961011
.\" Corrected return value, aeb, 970307
-.\" Added Single Unix Spec conversions and %z, aeb/esr, 990329.
+.\" Added Single UNIX Spec conversions and %z, aeb/esr, 990329.
.\" 2005-11-22 mtk, added Glibc Notes covering optional 'flag' and
.\" 'width' components of conversion specifications.
.\"
If the alternative format or specification does not exist for
the current locale, the behavior will be as if the unmodified
conversion specification were used. (SU)
-The Single Unix Specification mentions
+The Single UNIX Specification mentions
.BR %Ec ,
.BR %EC ,
.BR %Ex ,
.SH "CONFORMING TO"
SVr4, C89, C99.
There are strict inclusions between the set of conversions
-given in ANSI C (unmarked), those given in the Single Unix Specification
+given in ANSI C (unmarked), those given in the Single UNIX Specification
(marked SU), those given in Olson's timezone package (marked TZ),
and those given in glibc (marked GNU), except that
.B %+
In principle, this function does not initialize \fItm\fP but
only stores the values specified.
This means that \fItm\fP should be initialized before the call.
-Details differ a bit between different Unix systems.
+Details differ a bit between different UNIX systems.
The glibc implementation does not touch those fields which are not
explicitly specified, except that it recomputes the
.I tm_wday
.BR LOG_FTP ,
the other
.I facility
-values appear on most Unix systems.
+values appear on most UNIX systems.
The
.B LOG_PERROR
value for
.I option
is not specified by POSIX.1-2001, but is available
-in most versions of Unix.
+in most versions of UNIX.
.\" .SH HISTORY
.\" A
.\" .BR syslog ()
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH TOWCTRANS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH TOWLOWER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH TOWUPPER 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.SS "Ancient History"
There used to be a file
.I /etc/ttys
-in Unix V6, that was read by the
+in UNIX V6, that was read by the
.BR init (8)
program to find out what to do with each terminal line.
Each line consisted of three characters.
A hang on some line was solved by changing the \(aq1\(aq to a \(aq0\(aq,
signaling init, changing back again, and signaling init again.
.LP
-In Unix V7 the format was changed: here the second character
+In UNIX V7 the format was changed: here the second character
was the argument to
.BR getty (8)
indicating the sequence of line speeds to try (\(aq0\(aq was: cycle through
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,
+it returns 0 on UNIX V6 and V7 and BSD-like systems,
but \-1 on System V-like systems.
.SH "CONFORMING TO"
SUSv1; marked as LEGACY in SUSv2; removed in POSIX.1-2001.
.IR fttyslot ( fd ).
.\" .SH HISTORY
.\" .BR ttyslot ()
-.\" appeared in Unix V7.
+.\" appeared in UNIX V7.
.SH "SEE ALSO"
.BR getttyent (3),
.BR ttyname (3),
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH UNGETWC 3 1999-09-19 "GNU" "Linux Programmer's Manual"
The nonstandard
.BR *_unlocked ()
-variants occur on a few Unix systems, and are available in recent glibc.
+variants occur on a few UNIX systems, and are available in recent glibc.
.\" E.g., in HP-UX 10.0. In HP-UX 10.30 they are called obsolescent, and
.\" moved to a compatibility library.
.\" Available in HP-UX 10.0: clearerr_unlocked, fclose_unlocked,
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCPCPY 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCPNCPY 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCRTOMB 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSCASECMP 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSCAT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSCHR 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSCMP 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSCPY 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSCSPN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSDUP 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSLEN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSNCASECMP 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSNCAT 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSNCMP 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSNCPY 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSNLEN 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSNRTOMBS 3 2010-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSPBRK 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSRCHR 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSRTOMBS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSSPN 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSSTR 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSTOK 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCSTOMBS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCSWIDTH 3 2010-09-10 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCTOB 3 2009-02-04 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCTOMB 3 1999-07-25 "GNU" "Linux Programmer's Manual"
If \fIs\fP is NULL, the
.BR wctomb ()
function
-.\" The Dinkumware doc and the Single Unix specification say this, but
+.\" The Dinkumware doc and the Single UNIX specification say this, but
.\" glibc doesn't implement this.
resets the shift state, only known to this function,
to the initial state, and
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCTRANS 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WCTYPE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WCWIDTH 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WMEMCHR 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\"
.TH WMEMCMP 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.SH NAME
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WMEMCPY 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WMEMMOVE 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WMEMSET 3 1999-07-25 "GNU" "Linux Programmer's Manual"
.\" References consulted:
.\" GNU glibc-2 source code and manual
.\" Dinkumware C library reference http://www.dinkumware.com/
-.\" OpenGroup's Single Unix specification http://www.UNIX-systems.org/online.html
+.\" OpenGroup's Single UNIX specification http://www.UNIX-systems.org/online.html
.\" ISO/IEC 9899:1999
.\"
.TH WPRINTF 3 2010-09-20 "GNU" "Linux Programmer's Manual"
changed when required by this particular program.
Programs using these ioctl's will not be portable to other versions
-of Unix, will not work on older versions of Linux, and will not work
+of UNIX, will not work on older versions of Linux, and will not work
on future versions of Linux.
Use POSIX functions.
.IR /dev/ptmx ,
.I /dev/pts/*
.SH NOTES
-The Linux support for the above (known as Unix98 pty naming)
+The Linux support for the above (known as UNIX 98 pty naming)
is done using the
.I devpts
file system, that should be mounted on
.IR /dev/pts .
.LP
-Before this Unix98 scheme, master ptys were called
+Before this UNIX 98 scheme, master ptys were called
.IR /dev/ptyp0 ", ..."
and slave ptys
.IR /dev/ttyp0 ", ..."
Santa Cruz Operation,
.IR "System V Application Binary Interface" .
.PP
-Unix System Laboratories,
+UNIX System Laboratories,
"Object Files",
.IR "Executable and Linking Format (ELF)" .
.PP
by the Rock Ridge Interchange Protocol.
They are used to further describe the files in the
.B iso9660
-file system to a Unix host, and provide information such as long
+file system to a UNIX host, and provide information such as long
filenames, UID/GID, POSIX permissions, and devices.
It is automatically recognized within the
.B iso9660
.IR localhost ).
.PP
The Berkeley Internet Name Domain (BIND) Server implements the
-Internet name server for Unix systems.
+Internet name server for UNIX systems.
It augments or replaces the
.I /etc/hosts
file or hostname lookup, and frees a host from relying on
.I /proc/self/fd/N
is approximately the same as
.I /dev/fd/N
-in some Unix and Unix-like systems.
+in some UNIX and UNIX-like systems.
Most Linux MAKEDEV scripts symbolically link
.I /dev/fd
to
.\" CONFIG_PROC_PAGE_MONITOR
.TP
.I /proc/[pid]/root
-Unix and Linux support the idea of a per-process root of the
+UNIX and Linux support the idea of a per-process root of the
file system, set by the
.BR chroot (2)
system call.
.fi
.TP
.I /proc/net/unix
-Lists the Unix domain sockets present within the system and their
+Lists the UNIX domain sockets present within the system and their
status.
The format is:
.nf
of users of the socket, "Protocol" is currently always 0, "Flags"
represent the internal kernel flags holding the status of the
socket.
-Currently, type is always "1" (Unix domain datagram sockets are
+Currently, type is always "1" (UNIX domain datagram sockets are
not yet supported in the kernel).
\&"St" is the internal state of the
socket and Path is the bound path (if any) of the socket.
.IR console_loglevel .
.TP
.IR /proc/sys/kernel/pty " (since Linux 2.6.4)"
-This directory contains two files relating to the number of Unix 98
+This directory contains two files relating to the number of UNIX 98
pseudo-terminals (see
.BR pts (4))
on the system.
the user's current tty.
This facility was designed for a traditional time-sharing environment
-featuring character-cell terminals hardwired to a Unix minicomputer.
+featuring character-cell terminals hardwired to a UNIX minicomputer.
It is little used on modern workstation and personal Unixes.
.SH FILES
.TP
.\" I tried to be as much generic in the description as possible:
.\" - General boot sequence is applicable to almost any
.\" OS/Machine (DOS/PC, Linux/PC, Solaris/SPARC, CMS/S390)
-.\" - kernel and init(8) is applicable to almost any Unix/Linux
-.\" - boot scripts are applicable to SYSV-R4 based Unix/Linux
+.\" - kernel and init(8) is applicable to almost any UNIX/Linux
+.\" - boot scripts are applicable to SYSV-R4 based UNIX/Linux
.\"
.\" Modified 2004-11-03 patch from Martin Schulze <joey@infodrom.org>
.\"
.TP
Note:
The following description applies to System V release 4 based system, which
-currently covers most commercial Unix systems (Solaris, HP-UX, Irix, Tru64)
+currently covers most commercial UNIX systems (Solaris, HP-UX, Irix, Tru64)
as well as the major Linux distributions (Red Hat, Debian, Mandrake,
SUSE, Ubuntu).
Some systems (Slackware Linux, FreeBSD, OpenBSD)
directory (\fI/etc/sysconfig\fR on Red Hat systems) and are
used by the boot scripts.
-In older Unix systems, 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
capabilities \- overview of Linux capabilities
.SH DESCRIPTION
For the purpose of performing permission checks,
-traditional Unix implementations distinguish two categories of processes:
+traditional UNIX implementations distinguish two categories of processes:
.I privileged
processes (whose effective user ID is 0, referred to as superuser or root),
and
.TP
.B CAP_SETGID
Make arbitrary manipulations of process GIDs and supplementary GID list;
-forge GID when passing socket credentials via Unix domain sockets.
+forge GID when passing socket credentials via UNIX domain sockets.
.TP
.BR CAP_SETFCAP " (since Linux 2.6.24)"
Set file capabilities.
.BR setreuid (2),
.BR setresuid (2),
.BR setfsuid (2));
-make forged UID when passing socket credentials via Unix domain sockets.
+make forged UID when passing socket credentials via UNIX domain sockets.
.\" FIXME CAP_SETUID also an effect in exec(); document this.
.TP
.B CAP_SYS_ADMIN
.\" exec(), then it gets all capabilities in its
.\" permitted set, and no effective capabilities
This provides semantics that are the same as those provided by
-traditional Unix systems.
+traditional UNIX systems.
.SS Capability bounding set
The capability bounding set is a security mechanism that can be used
to limit the capabilities that can be gained during an
These IDs are used by the kernel to determine the permissions
that the process will have when accessing shared resources such
as message queues, shared memory, and semaphores.
-On most Unix systems, these IDs also determine the
+On most UNIX systems, these IDs also determine the
permissions when accessing files.
However, Linux uses the file system IDs described below
for this task.
to the same value.
Consequently, the file system IDs normally have the same values
as the corresponding effective ID, and the semantics for file-permission
-checks are thus the same on Linux as on other Unix systems.
+checks are thus the same on Linux as on other UNIX systems.
The file system IDs can be made to differ from the effective IDs
by calling
.BR setfsuid (2)
.B Q5
Can I send an
.B epoll
-file descriptor over a Unix domain socket to another process?
+file descriptor over a UNIX domain socket to another process?
.TP
.B A5
Yes, but it does not make sense to do this, since the receiving process
.SH NAME
glob \- Globbing pathnames
.SH DESCRIPTION
-Long ago, in Unix V6, there was a program
+Long ago, in UNIX V6, there was a program
.I /etc/glob
that would expand wildcard patterns.
Soon afterward this became a shell built-in.
archive all your files; \fItar\ c\ .\fP is better.)
.SS "Empty Lists"
The nice and simple rule given above: "expand a wildcard pattern
-into the list of matching pathnames" was the original Unix
+into the list of matching pathnames" was the original UNIX
definition.
It allowed one to have patterns that expand into
an empty list, as in
Of course ranges were originally meant to be ASCII ranges,
so that "\fI[\ \-%]\fP" stands for "\fI[\ !"#$%]\fP" and "\fI[a\-z]\fP" stands
for "any lowercase letter".
-Some Unix implementations generalized this so that a range X\-Y
+Some UNIX implementations generalized this so that a range X\-Y
stands for the set of characters with code between the codes for
X and for Y.
However, this requires the user to know the
hexadecimal
.SH DESCRIPTION
KOI8-R is the character set of choice for encoding Russian texts for
-many Unix-like operation systems.
+many UNIX-like operation systems.
KOI8-R is a successor for KOI-8, a
de-facto standard for Internet Mail, News, WWW and other interactive
services at least all over the ex-SU territory.
.SH NAME
path_resolution \- how a pathname is resolved to a file
.SH DESCRIPTION
-Some Unix/Linux system calls have as parameter one or more filenames.
+Some UNIX/Linux system calls have as parameter one or more filenames.
A filename (or pathname) is resolved as follows.
.SS "Step 1: Start of the resolution process"
If the pathname starts with the \(aq/\(aq character,
.B ENAMETOOLONG
error is returned ("File name too long").
.SS "Empty pathname"
-In the original Unix, the empty pathname referred to the current directory.
+In the original UNIX, the empty pathname referred to the current directory.
Nowadays POSIX decrees that an empty pathname must not be resolved
successfully.
Linux returns
.BR setfsgid (2).
.\" FIXME say something about file system mounted read-only ?
.SS "Bypassing permission checks: superuser and capabilities"
-On a traditional Unix system, the superuser
+On a traditional UNIX system, the superuser
.RI ( root ,
user ID 0) is all-powerful, and bypasses all permissions restrictions
when accessing files.
Linux provides both BSD-style and (standardized) System V-style
pseudo-terminals.
-System V-style terminals are commonly called Unix 98 pseudo-terminals
+System V-style terminals are commonly called UNIX 98 pseudo-terminals
on Linux systems.
Since kernel 2.6.4, BSD-style pseudo-terminals are considered deprecated
(they can be disabled when configuring the kernel);
-Unix 98 pseudo-terminals should be used in new applications.
-.SS "Unix 98 pseudo-terminals"
-An unused Unix 98 pseudo-terminal master is opened by calling
+UNIX 98 pseudo-terminals should be used in new applications.
+.SS "UNIX 98 pseudo-terminals"
+An unused UNIX 98 pseudo-terminal master is opened by calling
.BR posix_openpt (3).
(This function opens the master clone device,
.IR /dev/ptmx ;
.BR open (2).
The Linux kernel imposes a limit on the number of available
-Unix 98 pseudo-terminals.
+UNIX 98 pseudo-terminals.
In kernels up to and including 2.6.3, this limit is configured
at kernel compilation time
.RB ( CONFIG_UNIX98_PTYS ),
(slave),
where X is a letter from the 16-character set [p-za-e],
and Y is a letter from the 16-character set [0-9a-f].
-(The precise range of letters in these two sets varies across Unix
+(The precise range of letters in these two sets varies across UNIX
implementations.)
For example,
.I /dev/ptyp1
for "pty" in the name of the master) can then be opened.
.SH "FILES"
.I /dev/ptmx
-(Unix 98 master clone device)
+(UNIX 98 master clone device)
.br
.I /dev/pts/*
-(Unix 98 slave devices)
+(UNIX 98 slave devices)
.br
.I /dev/pty[p-za-e][0-9a-f]
(BSD master devices)
and (on architectures other than SPARC and MIPS)
.B SIGBUS
was to terminate the process (without a core dump).
-(On some other Unix systems 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,
.B SIGEMT
is not specified in POSIX.1-2001, but nevertheless appears
-on most other Unix systems,
+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 Unix systems 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 Unix systems.
+on several other UNIX systems.
Where defined,
.B SIGUNUSED
Because the range of available real-time signals varies according
to the glibc threading implementation (and this variation can occur
at run time according to the available kernel and glibc),
-and indeed the range of real-time signals varies across Unix systems,
+and indeed the range of real-time signals varies across UNIX systems,
programs should
.IR "never refer to real-time signals using hard-coded numbers" ,
but instead should always refer to real-time signals using the notation
.BR SA_RESTART
flag (see
.BR sigaction (2)).
-The details vary across Unix systems;
+The details vary across UNIX systems;
below, the details for Linux.
If a blocked call to one of the following interfaces is interrupted
rc startup (`run control') file, e.g., \fI.newsrc\fP
.TE
.SH "CONFORMING TO"
-General Unix conventions.
+General UNIX conventions.
.SH BUGS
This list is not exhaustive.
.SH "SEE ALSO"
HRTs are not supported on all hardware architectures.
(Support is provided on x86, arm, and powerpc, among others.)
.SS "The Epoch"
-Unix systems represent time in seconds since the
+UNIX systems represent time in seconds since the
.IR Epoch ,
1970-01-01 00:00:00 +0000 (UTC).
.RE
.TP
*
-Markus Kuhn: UTF-8 and Unicode FAQ for Unix/Linux.
+Markus Kuhn: UTF-8 and Unicode FAQ for UNIX/Linux.
.RS
http://www.cl.cam.ac.uk/~mgk25/unicode.html
.BR AF_LOCAL )
socket family is used to communicate between processes on the same machine
efficiently.
-Traditionally, Unix sockets can be either unnamed,
+Traditionally, UNIX sockets can be either unnamed,
or bound to a file system pathname (marked as being of type socket).
Linux also supports an abstract namespace which is independent of the
file system.
for a stream-oriented socket and
.BR SOCK_DGRAM ,
for a datagram-oriented socket that preserves message boundaries
-(as on most Unix implementations, Unix domain datagram
+(as on most UNIX implementations, UNIX domain datagram
sockets are always reliable and don't reorder datagrams);
and (since Linux 2.6.4)
.BR SOCK_SEQPACKET ,
for a connection-oriented socket that preserves message boundaries
and delivers messages in the order that they were sent.
-Unix sockets support passing file descriptors or process credentials
+UNIX sockets support passing file descriptors or process credentials
to other processes using ancillary data.
.SS Address Format
-A Unix domain socket address is represented in the following structure:
+A UNIX domain socket address is represented in the following structure:
.in +4n
.nf
Three types of address are distinguished in this structure:
.IP * 3
.IR pathname :
-a Unix domain socket can be bound to a null-terminated file
+a UNIX domain socket can be bound to a null-terminated file
system pathname using
.BR bind (2).
When the address of the socket is returned by
(Thus, there is a limit of 2^20 autobind addresses.)
.SS Sockets API
The following paragraphs describe domain-specific details and
-unsupported features of the sockets API for Unix domain sockets on Linux.
+unsupported features of the sockets API for UNIX domain sockets on Linux.
-Unix domain sockets do not support the transmission of
+UNIX domain sockets do not support the transmission of
out-of-band data (the
.B MSG_OOB
flag for
The
.BR send (2)
.B MSG_MORE
-flag is not supported by Unix domain sockets.
+flag is not supported by UNIX domain sockets.
The use of
.B MSG_TRUNC
.I flags
argument of
.BR recv (2)
-is not supported by Unix domain sockets.
+is not supported by UNIX domain sockets.
The
.B SO_SNDBUF
-socket option does have an effect for Unix domain sockets, but the
+socket option does have an effect for UNIX domain sockets, but the
.B SO_RCVBUF
option does not.
For datagram sockets, the
.BR dup (2).
.TP
.B SCM_CREDENTIALS
-Send or receive Unix credentials.
+Send or receive UNIX credentials.
This can be used for authentication.
The credentials are passed as a
.I struct ucred
search (execute) permission on the directory the socket is created in.
Connecting to the socket object requires read/write permission.
This behavior differs from many BSD-derived systems which
-ignore permissions for Unix sockets.
+ignore permissions for UNIX sockets.
Portable programs should not rely on
this feature for security.
in the file system that must be deleted by the caller when it is no
longer needed (using
.BR unlink (2)).
-The usual Unix close-behind semantics apply; the socket can be unlinked
+The usual UNIX close-behind semantics apply; the socket can be unlinked
at any time and will be finally removed from the file system when the last
reference to it is closed.
.BR recvmsg (2)
call.
-Unix domain stream sockets do not support the notion of out-of-band data.
+UNIX domain stream sockets do not support the notion of out-of-band data.
.SH EXAMPLE
See
.BR bind (2).
Within a relative path reference, the complete path segments "." and
".." have special meanings: "the current hierarchy level" and "the
level above this hierarchy level", respectively, just like they do in
-Unix-like systems.
+UNIX-like systems.
A path segment which contains a colon
character can't be used as the first segment of a relative URI path
(e.g., "this:that"), because it would be mistaken for a scheme name;
server requests a password, the program interpreting the URL
should request one from the user.
.PP
-Here are some of the most common schemes in use on Unix-like systems
+Here are some of the most common schemes in use on UNIX-like systems
that are understood by many tools.
Note that many tools using URIs also have internal schemes or specialized
schemes; see those tools' documentation for information on those schemes.
parenthesis and section number; see
.BR man (7)
for more information on the meaning of the section numbers.
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
An example is <man:ls(1)>.
.PP
This scheme refers to online info reference pages (generated from
texinfo files),
a documentation format used by programs such as the GNU tools.
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
As of this writing, GNOME and KDE differ in their URI syntax
and do not accept the other's syntax.
Only complete word matches are returned.
See
.BR whatis (1).
-This URI scheme is unique to Unix-like systems (such as Linux)
+This URI scheme is unique to UNIX-like systems (such as Linux)
and is not currently registered by the IETF.
.PP
.B "ghelp \- GNOME help documentation"
parts of many 16-bit characters bytes
like \(aq\\0\(aq or \(aq/\(aq which have a
special meaning in filenames and other C library function arguments.
-In addition, the majority of Unix tools expects ASCII files and can't
+In addition, the majority of UNIX tools expects ASCII files and can't
read 16-bit words as characters without major modifications.
For these reasons,
.B UCS-2
.B UCS
does not have these problems and is the common way in which
.B Unicode
-is used on Unix-style operating systems.
+is used on UNIX-style operating systems.
.SS Properties
The
.B UTF-8
projects / thirdparty / man-pages.git / commitdiff
