mirror of https://github.com/mkerrisk/man-pages
Wrap source lines so that new sentence starts on new line.
This commit is contained in:
parent
b4e9ee8f48
commit
20523df7ef
24
man1/intro.1
24
man1/intro.1
|
@ -225,17 +225,20 @@ removes a directory if it is empty, and complains otherwise.
|
|||
The command
|
||||
.I find
|
||||
(with a rather baroque syntax) will find files with given name
|
||||
or other properties. For example, "find . \-name tel" would find
|
||||
or other properties.
|
||||
For example, "find . \-name tel" would find
|
||||
the file "tel" starting in the present directory (which is called ".").
|
||||
And "find / \-name tel" would do the same, but starting at the root
|
||||
of the tree. Large searches on a multi-GB disk will be time-consuming,
|
||||
of the tree.
|
||||
Large searches on a multi-GB disk will be time-consuming,
|
||||
and it may be better to use
|
||||
.BR locate (1).
|
||||
.SS "Disks and Filesystems"
|
||||
The command
|
||||
.I mount
|
||||
will attach the file system found on some disk (or floppy, or CDROM or so)
|
||||
to the big file system hierarchy. And
|
||||
to the big file system hierarchy.
|
||||
And
|
||||
.I umount
|
||||
detaches it again.
|
||||
The command
|
||||
|
@ -253,8 +256,10 @@ will show you which processes are active and what numbers these
|
|||
processes have.
|
||||
The command
|
||||
.I kill
|
||||
allows you to get rid of them. Without option this is a friendly
|
||||
request: please go away. And "kill \-9" followed by the number
|
||||
allows you to get rid of them.
|
||||
Without option this is a friendly
|
||||
request: please go away.
|
||||
And "kill \-9" followed by the number
|
||||
of the process is an immediate kill.
|
||||
Foreground processes can often be killed by typing Control-C.
|
||||
.SS "Getting information"
|
||||
|
@ -275,13 +280,16 @@ In documentation it is customary to refer to man pages
|
|||
by giving the name and section number, as in
|
||||
.BR man (1).
|
||||
Man pages are terse, and allow you to find quickly some forgotten
|
||||
detail. For newcomers an introductory text with more examples
|
||||
detail.
|
||||
For newcomers an introductory text with more examples
|
||||
and explanations is useful.
|
||||
.LP
|
||||
A lot of GNU/FSF software is provided with info files. Type "info info"
|
||||
A lot of GNU/FSF software is provided with info files.
|
||||
Type "info info"
|
||||
for an introduction on the use of the program "info".
|
||||
.LP
|
||||
Special topics are often treated in HOWTOs. Look in
|
||||
Special topics are often treated in HOWTOs.
|
||||
Look in
|
||||
.I /usr/share/doc/howto/en
|
||||
and use a browser if you find HTML files there.
|
||||
.\"
|
||||
|
|
|
@ -169,7 +169,8 @@ These are faults where the page has to be read in from disk.
|
|||
.B %R
|
||||
Number of minor, or recoverable, page faults.
|
||||
These are faults for pages that are not valid but which have
|
||||
not yet been claimed by other virtual pages. Thus the data
|
||||
not yet been claimed by other virtual pages.
|
||||
Thus the data
|
||||
in the page is still valid but the system tables must be updated.
|
||||
.TP
|
||||
.B %W
|
||||
|
|
|
@ -389,8 +389,8 @@ permission bit (see
|
|||
and
|
||||
.BR chmod (2)).
|
||||
|
||||
The Linux implementation of mandatory locking is unreliable. See BUGS
|
||||
below.
|
||||
The Linux implementation of mandatory locking is unreliable.
|
||||
See BUGS below.
|
||||
.SS "Managing signals"
|
||||
.BR F_GETOWN ", " F_SETOWN ", " F_GETSIG " and " F_SETSIG
|
||||
are used to manage I/O availability signals:
|
||||
|
|
|
@ -673,7 +673,8 @@ l l l l.
|
|||
|
||||
// More arguments.
|
||||
Some ioctl's take a pointer to a structure which contains additional
|
||||
pointers. These are documented here in alphabetical order.
|
||||
pointers.
|
||||
These are documented here in alphabetical order.
|
||||
|
||||
.B CDROMREADAUDIO
|
||||
takes an input pointer
|
||||
|
|
|
@ -381,7 +381,8 @@ of size
|
|||
.IR buflen .
|
||||
After the call,
|
||||
.I result
|
||||
will point to the result on success. In case of an error
|
||||
will point to the result on success.
|
||||
In case of an error
|
||||
or if no entry is found
|
||||
.I result
|
||||
will be NULL.
|
||||
|
|
Loading…
Reference in New Issue