Command Reference Guide
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/introduction.9
________________________________________________________________
___ ___
introduction(9) introduction(9)
Section 2: System Calls
Entries into the HP-UX kernel, including the C-language interface. These topics are primarily of
interest to programmers.
Section 3: Library Functions
Available subroutines that reside (in binary form) in various system libraries. These topics are pri-
marily of interest to programmers.
Section 4: File Formats
The structure of various types of files, primarily of interest to administrators and programmers. For
example, the link editor output file format is described in a.out(4). Files that are used only by a single
command (such as intermediate files used by assemblers) are not described. C-language declarations
corresponding to the formats in Section 4 can be found in the directories /usr/include and
/usr/include/sys.
Section 5: Miscellaneous
A variety of information, such as descriptions of header files, character sets, macro packages, and
other topics.
Section 7: Device Special Files
The characteristics of special (device) files that provide the link between HP-UX and system I/O dev-
ices. The names for each topic usually refer to the type of I/O device rather than to the names of indi-
vidual special files.
Section 9: Introduction and Glossary
A general introduction (this one) and definitions of terms used in the HP-UX environment.
Composite Index (Printed Manual)
An alphabetical listing of keywords and topics based on the NAME section near the beginning of each
manpage as well as other information, cross-referenced to manpage names and sections. The index
also contains references to built-infeatures in the various command interpreters ("shells").
MANPAGE FORMATS
All manpages follow an establishedsection heading format, but not all section headings are included in each
manpage. A few manpages have self-explanatory specialized headings.
NAME
Gives the names of the commands, functions, or features and briefly states the purpose.
SYNOPSIS
Summarizes the syntax of the command or program entity. A few conventions are used:
Constant-width characters indicate literal characters that should be entered exactly as they
appear. These characters appear in bold in the online manpages.
Italic strings represent variable elements that should be replaced with appropriate values.
Roman square brackets ([]) indicate that the contents are optional.
Roman braces ({}) indicate a required element, usually in a choice.
Ellipses (...) indicate that the previous element can be repeated.
Note: An argument beginning with a dash (-), a plus sign (+), or an equal sign (
=) is often defined as
a command option, even if it appears in a position where a file name could appear. Therefore, it is
unwise to have files names that begin with
-, +,or=.
DESCRIPTION
Discusses the function and behavior of each entry.
EXTERNAL INFLUENCES
Information under this heading pertains to programming for various spoken languages. Typical
entries indicate support for single- or multibyte characters, the effect of language-related environment
variables on system behavior, and other related information.
NETWORKING FEATURES
Information under this heading is applicable only if you are using the network feature described there
Introduction−−2 − 2 − HP-UX Release 11i: December 2000
___
___