Return to whatis.1 CVS log

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

Annotation of 43BSDTahoe/man/man1/whatis.1, revision 1.1

1.1     ! root        1: .\" Copyright (c) 1980, 1987 Regents of the University of California.
        !             2: .\" All rights reserved.  The Berkeley software License Agreement
        !             3: .\" specifies the terms and conditions for redistribution.
        !             4: .\"
        !             5: .\"    @(#)whatis.1    6.4 (Berkeley) 6/30/87
        !             6: .\"
        !             7: .TH WHATIS 1 "June 30, 1987"
        !             8: .UC 4
        !             9: .SH NAME
        !            10: whatis \- describe what a command is
        !            11: .SH SYNOPSIS
        !            12: .B whatis
        !            13: [
        !            14: .B -M
        !            15: .I path
        !            16: ]
        !            17: command ...
        !            18: .SH DESCRIPTION
        !            19: \fIWhatis\fP looks up a given command and gives the header line from the
        !            20: manual page.  You can then use the \fIman\fP(1) command to get more
        !            21: information.
        !            22: .PP
        !            23: Normally \fIwhatis\fP checks in a standard location (/usr/man) for its
        !            24: database ``whatis''.  This can be changed by supplying a \fIpath\fP (a
        !            25: la the Bourne shell) with the \fB-M\fP flag.  This search path must be
        !            26: a colon (``:'') separated list of directories which \fIwhatis\fP will
        !            27: search for files named ``whatis''.  The path can also be set with the
        !            28: environmental variable \fIMANPATH\fP.
        !            29: .SH FILES
        !            30: .DT
        !            31: /usr/man/whatis                data base
        !            32: .SH "SEE ALSO"
        !            33: apropos(1), man(1)

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