Return to intro.1 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man1

Annotation of 43BSDTahoe/man/man1/intro.1, revision 1.1.1.1

1.1       root        1: .\"    @(#)intro.1     6.1 (Berkeley) 4/29/85
                      2: .\"
                      3: .TH INTRO 1 "April 29, 1985"
                      4: .AT 3
                      5: .SH NAME
                      6: intro \- introduction to commands
                      7: .SH DESCRIPTION
                      8: This section describes publicly accessible commands in alphabetic order.
                      9: Certain distinctions of purpose are made in the headings:
                     10: .TP
                     11: (1)
                     12: Commands of general utility.
                     13: .TP
                     14: (1C)
                     15: Commands for communication with other systems.
                     16: .TP
                     17: (1G)
                     18: Commands used primarily for graphics and computer-aided design.
                     19: .PP
                     20: N.B.: Commands related to system maintenance used to appear in
                     21: section 1 manual pages and were distinguished by (1M) at the top of the
                     22: page.  These manual pages now appear in section 8.
                     23: .SH SEE ALSO
                     24: Section (6) for computer games.
                     25: .PP
                     26: .I How to get started,
                     27: in the Introduction.
                     28: .SH DIAGNOSTICS
                     29: Upon termination each command returns two bytes of status,
                     30: one supplied by the system giving the cause for
                     31: termination, and (in the case of `normal' termination)
                     32: one supplied by the program, see
                     33: .I wait
                     34: and
                     35: .IR exit (2).
                     36: The former byte is 0 for normal termination, the latter
                     37: is customarily 0 for successful execution, nonzero
                     38: to indicate troubles such as erroneous parameters, bad or inaccessible data,
                     39: or other inability to cope with the task at hand.
                     40: It is called variously `exit code', `exit status' or
                     41: `return code', and is described only where special conventions are involved.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.