home *** CD-ROM | disk | FTP | other *** search
-
-
-
- IIIINNNNTTTTRRRROOOO((((1111)))) IIIINNNNTTTTRRRROOOO((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- intro - introduction to commands, application programs, and programming
- commands.
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- This section describes, in alphabetical order, publicly-accessible
- commands. Certain distinctions of purpose are made in the headings:
-
- (1) Commands of general utility.
- (1C) Commands for communication with other systems.
- (1G) Graphics utilities.
-
- MMMMaaaannnnuuuuaaaallll PPPPaaaaggggeeee CCCCoooommmmmmmmaaaannnndddd SSSSyyyynnnnttttaaaaxxxx
- Unless otherwise noted, commands described in the SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS section of a
- manual page accept options and other arguments according to the following
- syntax and should be interpreted as explained below.
-
- _n_a_m_e [ ----_o_p_t_i_o_n ... ] [ _c_m_d_a_r_g ... ]
- where:
-
- [ ] Surround an _o_p_t_i_o_n or _c_m_d_a_r_g that is not required.
-
- ... Indicates multiple occurrences of the _o_p_t_i_o_n or _c_m_d_a_r_g.
-
- _n_a_m_e The name of an executable file.
-
- _o_p_t_i_o_n This is either
- _n_o_a_r_g_l_e_t_t_e_r...
- or
- _a_r_g_l_e_t_t_e_r _o_p_t_a_r_g[,,,,...]
- It is always preceded by a ``-''.
-
- _n_o_a_r_g_l_e_t_t_e_r
- A single letter representing an option without an option-
- argument. Note that more than one _n_o_a_r_g_l_e_t_t_e_r option can be
- grouped after one ``----'' (Rule 5, below).
-
- _a_r_g_l_e_t_t_e_r
- A single letter representing an option requiring an option-
- argument.
-
- _o_p_t_a_r_g An option-argument (character string) satisfying a preceding
- _a_r_g_l_e_t_t_e_r. Note that groups of _o_p_t_a_r_g_s following an
- _a_r_g_l_e_t_t_e_r must be separated by commas, or separated by white
- space and quoted (Rule 8, below).
-
- _c_m_d_a_r_g Path name (or other command argument) _n_o_t beginning with
- ``----'', or ``----'' by itself indicating the standard input.
-
- CCCCoooommmmmmmmaaaannnndddd SSSSyyyynnnnttttaaaaxxxx SSSSttttaaaannnnddddaaaarrrrdddd:::: RRRRuuuulllleeeessss
- These command syntax rules are not followed by all current commands, but
- all new commands will obey them. _g_e_t_o_p_t_s(1) should be used by all shell
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- IIIINNNNTTTTRRRROOOO((((1111)))) IIIINNNNTTTTRRRROOOO((((1111))))
-
-
-
- procedures to parse positional parameters and to check for legal options.
- It supports Rules 3-10 below. The enforcement of the other rules must be
- done by the command itself.
-
- Since almost all commands are run via the shells ( _b_s_h(1),_s_h(1),_c_s_h(1),
- _k_s_h(1),_a_n_d _t_c_s_h(_1)) diagnostic messages may be issued by the shells,
- prior to, or even instead of, the command itself being executed. A
- common case is too many arguments to the command. See the manual page
- for your shell for details.
-
- 1. Command names (_n_a_m_e above) must be between two and nine
- characters long.
-
- 2. Command names must include only lower-case letters and digits.
-
- 3. Option names (_o_p_t_i_o_n above) must be one character long.
-
- 4. All options must be preceded by ``----''.
-
- 5. Options with no arguments may be grouped after a single ``----''.
-
- 6. The first option-argument (_o_p_t_a_r_g above) following an option
- must be preceded by white space.
-
- 7. Option-arguments cannot be optional.
-
- 8. Groups of option-arguments following an option must either be
- separated by commas or separated by white space and quoted
- (e.g., -o xxx,z,yy or -o "xxx z yy").
-
- 9. All options must precede operands (_c_m_d_a_r_g above) on the command
- line.
-
- 10. ``--------'' may be used to indicate the end of the options.
-
- 11. The order of the options relative to one another should not
- matter.
-
- 12. The relative order of the operands (_c_m_d_a_r_g above) may affect
- their significance in ways determined by the command with which
- they appear.
-
- 13. ``----'' preceded and followed by white space should only be used
- to mean standard input.
-
- Throughout the manual pages there are references to _T_M_P_D_I_R, _B_I_N_D_I_R,
- _I_N_C_D_I_R, _L_I_B_D_I_R, and _L_L_I_B_D_I_R. These represent directory names whose
- value is specified on each manual page as necessary. For example,
- _T_M_P_D_I_R might refer to /tmp or /usr/tmp. These are not environment
- variables and cannot be set. (There is also an environment variable
- called TTTTMMMMPPPPDDDDIIIIRRRR which can be set. See _t_m_p_n_a_m(3S).)
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- IIIINNNNTTTTRRRROOOO((((1111)))) IIIINNNNTTTTRRRROOOO((((1111))))
-
-
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- getopts(1), exec(2), exit(2), wait(2), getopt(3C).
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- 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 _w_a_i_t(2) and
- _e_x_i_t(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, or bad or inaccessible data. It is called
- variously ``exit code'', ``exit status'', or ``return code'', and is
- described only where special conventions are involved.
- WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS
- Some commands produce unexpected results when processing files containing
- null characters. These commands often treat text input lines as strings
- and therefore become confused upon encountering a null character (the
- string terminator) within a line.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-