- The manual pages:
man <command> - A command’s short usage summary:
<command> --help - The GNU info system:
info <command>
Man pages are the canonical local reference on RHEL. Use
--help for quick usage summaries and info when a program provides more verbose, tutorial-style documentation.man pages: structure and navigation
Man pages (theman system) provide detailed reference material for commands, configuration files, system calls, libraries, and administration tools. Typical sections of a man page include:
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- EXAMPLES
- FILES
- SEE ALSO
less pager by default):
- Space — scroll down one page
- Enter — scroll down one line
- b or B — scroll up one page
/pattern— search forward for pattern- n — repeat search in same direction
- N — repeat search in opposite direction
- g — jump to top of page
- G — jump to bottom of page
- q — quit the man page
You can request a specific section; for example:
Example: viewing the ls manual
To read the ls man page:
info:
Searching the manual database
If you only know a keyword but not the exact command name,man -k (or apropos) searches the man short descriptions (the whatis database):
man -k returns nothing useful, the manual index might be out of date. Rebuild the man database with mandb; this typically requires root privileges:
mandb must be run with appropriate privileges (usually via sudo or as root) to rebuild the system man database. Running it as an unprivileged user will not update the global index.useradd to create new users).
Examples of section disambiguation
Some names appear in multiple man sections. Use the section number to pick the intended topic:Package-specific documentation: /usr/share/doc
Not all documentation lives in man pages. Many installed packages place additional files under/usr/share/doc. These directories often contain README files, FAQs, examples, and sometimes HTML documentation.
List installed package documentation:
INTRO, README, and FAQ can provide background material, configuration examples, and troubleshooting hints that are not always present in man pages.
Tips and best practices
- Use
manfor authoritative, on-system references and exact option syntax. - Use
--helpfor quick summaries and common options. - Use
infofor programs that offer more tutorial-style documentation. - Use
man -koraproposto find commands by keyword. If results look stale, runsudo mandbto rebuild the index. - Search inside man pages with
/patternand navigate between matches withnandN. - Look for an EXAMPLES section in complex man pages — practical examples are often the fastest way to learn how to use a command.
- When scripting or automating, prefer reading the SYNOPSIS and OPTIONS sections to avoid unexpected behavior.
Further reading and references
- Red Hat Enterprise Linux Documentation
man— local manual pages on your system (man man)- GNU info manual: https://www.gnu.org/software/texinfo/manual/info.html
man, --help, info, man -k/apropos, mandb, and files under /usr/share/doc. You do not need to memorize everything — learn how to find authoritative details quickly and apply them when you need them.