Share this Page URL

Chapter 12. Introducing the BSD Subsystem > The Unix File System - Pg. 464

Introducing the BSD Subsystem -h -w -C <file> -M <path> -m <path> -k <keyword> Displays the SYNOPSIS lines of the requested manual pages. 464 Lists the pathnames of manual pages that would be displayed for the specified section and name combination. Uses the specified file instead of the default configuration file. This allows users to configure their own manual environment. See man.conf(5) for more details. Overrides the list of standard directories where man searches for manual pages. The path specified must be a colon-separated list of directories. The search path may also be specified by the MANPATH environment variable. Adds to the list of standard search directories. The path specified must be a colon-separated list of directories. These directories are searched before the standard list or directories specified by -M or MANPATH. Displays a list of manual pages that contain the <keyword>. The optional <section> argument restricts man's search to the specified section. The Unix File System To the novice Unix user--especially one coming from a GUI environment as nice as the Mac's-- venturing into the Unix file system will probably feel like a journey back to the Stone Age. Files upon files, nothing to indicate what any of them do, and not a friendly icon in sight. Although the file system might initially appear cryptic and primitive, you will find that with experience, it actually affords you considerable sophistication and control. This sophistication comes from the ability to combine the functions of many small programs into larger programs with arbitrarily complex functions. Before the use of most Unix commands will make sense, you'll need to understand a few things about the design of the Unix file system. The Mac OS X HFS+ file system doesn't strictly adhere to the model that most Unixes use, but from the point of view of the BSD subsystem, it functions in an analogous manner. You'll find a number of differences between the way Unix thinks of files, and what you're probably used to, but after you get used to them, you'll probably find these differences are to your liking.