Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ intro(1M) — CX/UX 6.20

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

getopt(1)

getopt(3C)

intro(1M)

NAME

intro − intro to system maintenance commands & application programs

DESCRIPTION

This section describes, in alphabetical order, commands that are used chiefly for system maintenance and administration purposes.  The commands in this section should be used along with those listed in Section 1 of the CX/UX User’s Reference Manual and Sections 2, 3, 4, and 5 of the CX/UX Programmer’s Reference Manual. 

COMMAND SYNTAX

Unless otherwise noted, commands described in this section accept options and other arguments according to the following syntax:

name [option(s)] [cmdarg(s)]
where:

name The name of an executable file. 

option − noargletter(s) or,
− argletter<>optarg
where <> is optional white space.

noargletter A single letter representing an option without an argument. 

argletter A single letter representing an option requiring an argument. 

optarg Argument (character string) satisfying preceding argletter.

cmdarg Path name (or other command argument) not beginning with − or, − by itself indicating the standard input. 

SEE ALSO

getopt(1), getopt(3C). 
CX/UX User’s Reference Manual.
CX/UX Programmer’s Reference Manual.
CX/UX System Administration Manual.

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 wait(2) and 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. 

BUGS

Regretfully, many commands do not adhere to the aforementioned syntax. 

CX/UX Administrator’s Reference

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026