Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
howtos:general_admin:searching_and_reading_manpages_efficiently [2012/11/07 14:04 (UTC)]
markush 		howtos:general_admin:searching_and_reading_manpages_efficiently [2013/01/06 00:13 (UTC)]
mfillpot added REVIEWED comment
Line 1: Line 1:
 +<!-- Reviewed 2012-12-31 hazel -->
 <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). -->
 ====== How to search and read Manpages efficiently ====== ====== How to search and read Manpages efficiently ======
  
-I hope this Howto can help some of you, although I'm aware that many of the readers are already familiar with this subject.+Manpages are pages in the online Unix Manual. I hope this Howto can help some of you to use them more effectively, although I'm aware that many of the readers are already familiar with this subject.
  
 ===== Searching for a Manpage ===== ===== Searching for a Manpage =====
Line 9: Line 10:
   * ''man -k''   * ''man -k''
   * ''whatis''   * ''whatis''
-''apropos'' is only an alias for ''man -k'' there is no difference between them. The difference between ''whatis'' and the other commands is that ''whatis'' searches for whole words whereas ''apropos'' (or ''man -k'' respectively) searches for parts of strings. +''apropos'' is only an alias for ''man -k''; there is no difference between them. The difference between ''whatis'' and the other commands is that ''whatis'' searches for whole words whereas ''apropos'' (or ''man -k'' respectively) searches for parts of strings. 
  
 If you don't know how exactly a word, for example a command, is written, you can use ''apropos''. If you know exactly the word to search for, ''whatis'' would be more efficient because it results in fewer lines of output. If you don't know how exactly a word, for example a command, is written, you can use ''apropos''. If you know exactly the word to search for, ''whatis'' would be more efficient because it results in fewer lines of output.
Line 40: Line 41:
 dhcp []              (5)  - options - Dynamic Host Configuration Protocol options  dhcp []              (5)  - options - Dynamic Host Configuration Protocol options 
 </code> </code>
-Both commands search case-insensitive!+For both commands, the search is case-insensitive!
  
 ===== Updating the ''whatis'' Database ===== ===== Updating the ''whatis'' Database =====
-The ''whatis''command has its own database. The manpages for any packages of the stock Slackware installation are already present in the database. This is also true if you upgrade such packages. But if you build your own packages from source, for example from [[http://www.slackbuilds.org|SlackBuilds.org]], the manpages of this packages are not yet present in the ''whatis'' database. In order to update the database after installing new packages Slackware provides the ''makewhatis'' command. It has to be executed as root.+The ''whatis''command has its own database. The manpages for any packages of the stock Slackware installation are already present in the database. This is also true if you upgrade such packages. But if you build your own packages from source, for example from [[http://www.slackbuilds.org|SlackBuilds.org]], the manpages for these packages are not yet present in the ''whatis'' database. In order to update the database after installing new packages, Slackware provides the ''makewhatis'' command. It has to be executed as root.
  
-Please note that other distributions possibly use the ''mandb'' command which does the same.+Please note that some other distributions use the ''mandb'' command for this purpose.
  
-===== The Sectioning of the Manpages ===== +===== Sections in the Manual ===== 
-Don't confuse the sectioning of the manpages with the uniform structure of each manpage, this is described in the paragraph below.+Don't confuse these sections with the sections within the structure of each manpage; they are described in the paragraph below.
  
-The manpages are divided into eight different sections. Here is an extract from the manpage for the ''man'' command.+The manpages manual is divided into eight different sections. Here is an extract from the manpage for the ''man'' command.
 <code> <code>
 MANUAL SECTIONS  MANUAL SECTIONS 
Line 60: Line 61:
        5      File Formats and Conventions         5      File Formats and Conventions 
        6      Games et. Al.         6      Games et. Al. 
-       7      Miscellanea  +       7      Miscellanea 
-       8      System Administration tools and Deamons+       8      System Administration tools and Daemons
 </code> </code>
-If the manualpages for a topic are divided over different sections, one can pass the section number as an argument to the ''man'' command.+If the manual pages for a topic are divided over different sections, one can pass the section number as an additional argument to the ''man'' command.
 === Example === === Example ===
 <code> <code>
Line 81: Line 82:
  
 ===== The Structure of the Manpages ===== ===== The Structure of the Manpages =====
-The manpages have (should have) all the same structure:+The manpages all have (or should have) the same structure:
   * Name   * Name
-    * Name of the command and a short description about it's function(s)+    * Name of the command and a short description of its function(s)
   * Synopsis   * Synopsis
-    * A short list of the options and the synopsis+    * A usage statement including a short list of the options
   * Description   * Description
-    * The detailed explanation of the command +    * A detailed explanation of the command 
   * Options   * Options
-    * Detailed explanation of the commandline-options for the command+    * Detailed explanation of the command line options for the command
   * Bugs   * Bugs
     * Known Bugs       * Known Bugs  
Line 108: Line 109:
  
 ===== Navigation within a Manpage ===== ===== Navigation within a Manpage =====
-Navigation is like in vi: +Navigation commands are like those in vi: 
   * ''G'' end of the manpage    * ''G'' end of the manpage 
   * ''gg'' first line of the mapage   * ''gg'' first line of the mapage
Line 120: Line 121:
 ===== Formatting a Manpage as a PDF-document ===== ===== Formatting a Manpage as a PDF-document =====
 If you want to have a manpage as a PDF document you can use the command: If you want to have a manpage as a PDF document you can use the command:
-<code>man -t ls | ps2pdf ->ls-manpage.pdf</code>+<code>man -t ls | ps2pdf - > ls-manpage.pdf</code>
 which formats the manpage for the ''ls'' command into a pdf document named "ls-manpage.pdf". which formats the manpage for the ''ls'' command into a pdf document named "ls-manpage.pdf".
  
 ===== Further Reading ===== ===== Further Reading =====
-For more information read the manpage for the ''man'' command and read the manpages listed in "see also".+For more information read the manpage for the ''man'' command and the manpages listed in "see also".
 ====== Sources ====== ====== Sources ======
 <!-- If you are copying information from another source, then specify that source --> <!-- If you are copying information from another source, then specify that source -->
Line 134: Line 135:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must remove the tag-word "template" below before saving your new page --> <!-- You must remove the tag-word "template" below before saving your new page -->
-{{tag>howtos manpages searching documentation information }}+{{tag>howtos manpages searching documentation information author_markush }}

In Other Languages
QR Code
QR Code howtos:general_admin:searching_and_reading_manpages_efficiently (generated for current page)