SysIII/usr/src/man/man1/intro.1

Compare this file to the similar file:
Show the results in this format:

.TH INTRO 1
.SH NAME
intro \- introduction to commands and application programs
.SH DESCRIPTION
This section describes, in alphabetical order, publicly-accessible commands.
Certain distinctions of purpose are made in the headings:
.TP
(1)
Commands of general utility.
.PD 0
.TP
(1C)
Commands for communication with other systems.
.TP
(1G)
Commands used primarily for graphics and computer-aided design.
.TP
(1M)
Commands used primarily for system maintenance.
.PD
.SH COMMAND SYNTAX
Unless otherwise noted, commands described in this section accept options and
other arguments according to the following syntax:
.PP
.I name
.RI [ option ( s )]
.RI [ cmdarg ( s )]
.br
where:
.TP 13
.I name
The name of an executable file.
.TP
.I option\^
.B \-
.IR noargleter ( s )     
or,
.br
.B \-
.IR argletter <> optarg
.br
where <> is optional white space.
.TP
.I noargletter\^
A single letter representing an option without an argument.
.TP
.I argletter\^
A single letter representing an option requiring an argument.
.TP
.I optarg\^
Argument (character string) satisfying preceding
.IR argletter .
.TP
.I cmdarg\^
Path name (or other command argument)
.I not\^
beginning with
.B \-
or,
.B \-
by itself indicating the standard input.
.SH SEE ALSO
getopt(1), getopt(3C).
.br
Section\ 6 of this volume for computer games.
.PD 0
.PP
.IR "How to Get Started" ,
at the front of this volume.
.PD
.SH DIAGNOSTICS
Upon termination, each command returns two bytes of status,
one supplied by the system and giving the cause for
termination, and (in the case of ``normal'' termination)
one supplied by the program
(see
.IR wait (2)
and
.IR exit (2)).
The former byte is 0 for normal termination; the latter
is customarily 0 for successful execution and non-zero
to indicate troubles such as erroneous parameters, bad or inaccessible data,
or other inability to cope with the task at hand.
It is called variously ``exit code'', ``exit status'', or
``return code'', and is described only where special
conventions are involved.
.SH BUGS
Regretfully, many commands do not adhere to the aforementioned syntax.