21 lines
3.0 KiB
HTML
21 lines
3.0 KiB
HTML
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>man page</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../M.html" title="M"/><link rel="previous" href="malware.html" title="malware"/><link rel="next" href="management.html" title="management"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">man page</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="malware.html">Prev</a> </td><th width="60%" align="center">M</th><td width="20%" align="right"> <a accesskey="n" href="management.html">Next</a></td></tr></table><hr/></div><dt><a id="man-page"/><dt xmlns="" id="man-page"><b>man page</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p>A page from the Unix Programmer's Manual,
|
||
documenting one of Unix's many commands, system calls,
|
||
library subroutines, device driver interfaces, file formats,
|
||
games, macro packages, or maintenance utilities.
|
||
By extension, the term “<span class="quote">man page</span>” may be used to refer to
|
||
documentation of any kind, under any system, though it is most likely to be
|
||
confined to short on-line references.</p><p>As mentioned in <a href="../conventions.html" title="Chapter 11. Other Lexicon Conventions">Chapter 11, <i>Other Lexicon Conventions</i></a>, there is a
|
||
standard syntax for referring to man page entries: the phrase
|
||
“<span class="quote">foo(n)</span>” refers to the page for “<span class="quote">foo</span>” in chapter
|
||
n of the manual, where chapter 1 is user commands, chapter 2 is system
|
||
calls, etc.</p><p>The man page format is beloved, or berated, for having the same sort
|
||
of pithy utility as the rest of Unix. Man pages tend to be written as very
|
||
compact, concise descriptions which are complete but not forgiving of the
|
||
lazy or careless reader. Their stylized format does a good job of
|
||
summarizing the essentials: invocation syntax, options, basic
|
||
functionality. While such a concise reference is perfect for the
|
||
do-one-thing-and-do-it-well tools which are favored by the Unix philosophy,
|
||
it admittedly breaks down when applied to a command which is itself a major
|
||
subsystem.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="malware.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../M.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="management.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">malware </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> management</td></tr></table></div></body></html>
|