UNRSL On-Line Manual Search

Use the form below to search the on-line manual pages of the UNR Seismology UNIX computer systems.

Note: This is an HTML form. You must have a browser that supports forms in order to use it. If you do not see a text editing area below, your browser does not support forms.

Netscape Communications Corp., among others, can supply forms-capable browsers for Mac, Windows, and UNIX platforms.

On-Line Manual Search Command:

Please allow a few minutes for each search

Composing a Search Command

Search commands are case sensitive. To read the on-line manual page of a command command whose name you know, enter simply:

command

If you want to search for a manual page named command that you know resides in a particular numbered section n of the on-line manual, enter:

n command

To find what manual pages in what sections may pertain to a keyword keyword that you are interested in, enter:

-k keyword

The on-line manual contains information on UNR Seismology UNIX system operating commands, software packages, and hardware that is not automatically available on the Web or by FTP. As such this search is probably useless to anyone who does not have a UNR Seismology UNIX account. If you do, however, this page will give you quick access to all available manual pages, including local ones.

The on-line manual, wherever pieces of it happen to be installed, is thought to be divided into nine sections:

1 - user commands, applications (here including most local and 3rd-party applications)
2 - system calls (for programmers)
3 - function calls (math, TCP, etc. libraries; for programmers)
4 - devices and network interfaces (low level)
5 - file formats
6 - games and demos (very primitive)
7 - environments, tables, and troff macros
8 - maintenance commands (for system administrators)
l - local man pages

A search for either the page of a known command or a keyword will always look through all sections. You will need to use the section number in those few cases where an entry you want from outside section 1 happens to have the same name as an entry in section 1.