Wrapped source lines

This commit is contained in:
Michael Kerrisk 2007-05-12 12:58:31 +00:00
parent 95f76e3b77
commit 7c93fec03d
6 changed files with 13 additions and 7 deletions

View File

@ -219,7 +219,8 @@ or a write
lock on a file.
Any number of processes may hold a read lock (shared lock)
on a file region, but only one process may hold a write lock
(exclusive lock). An exclusive lock excludes all other locks,
(exclusive lock).
An exclusive lock excludes all other locks,
both shared and exclusive.
A single process can hold only one type of lock on a file region;
if a new lock is applied to an already-locked region,

View File

@ -155,7 +155,8 @@ can be used only on regions of memory obtained from
On Linux it is always legal to call
.BR mprotect ()
on any address in a process' address space (except for the
kernel vsyscall area). In particular it can be used
kernel vsyscall area).
In particular it can be used
to change existing code mappings to be writable.
Whether

View File

@ -150,7 +150,8 @@ is changed by file accesses, e.g. by
.BR utime (2)
and
.BR read (2)
(of more than zero bytes). Other routines, like
(of more than zero bytes).
Other routines, like
.BR mmap (2),
may or may not update
.IR st_atime .

View File

@ -134,8 +134,8 @@ No checking of
is done.
Deleting the name referred to by a symlink will actually delete the
file (unless it also has other hard links). If this behaviour is not
desired, use
file (unless it also has other hard links).
If this behaviour is not desired, use
.BR link (2).
.SH "CONFORMING TO"
SVr4, 4.3BSD, POSIX.1-2001.

View File

@ -45,7 +45,9 @@ For output streams this discards any unwritten output.
For input streams this discards any input read from the underlying object
but not yet obtained via
.BR getc (3);
this includes any text pushed back via \fIungetc\fP(3). See also
this includes any text pushed back via
.BR ungetc (3).
See also
.BR fflush (3).
.LP
The function

View File

@ -275,7 +275,8 @@ A possible system installation scenario is as follows:
.IR /linuxrc
determines what is needed to (1) mount the normal root file-system
(i.e. device type, device drivers, file system) and (2) the
distribution media (e.g. CD-ROM, network, tape, ...). This can be
distribution media (e.g. CD-ROM, network, tape, ...).
This can be
done by asking the user, by auto-probing, or by using a hybrid
approach.
.PP