Navigating System Documentation with Man and Info

1. The man Command: Your Go-To Manual

The man command (short for "manual") is the traditional and most common way to access documentation on a Linux system. Nearly every command, utility, and even configuration file has an associated "man page".

To view a man page, you simply type man followed by the name of the command you want to learn about.

Try it now:

man ls

This will open the manual for the ls command, which is used to list directory contents. You'll see a wall of text displayed in a "pager" program, which is usually less. Let's learn how to navigate it.

Navigating Man Pages

Navigating these pages efficiently is a key skill. While you can use your mouse wheel or Page Up/Down keys, learning the standard keyboard shortcuts will make you much faster.

Practice these navigation and search commands in the man ls page. For example, try searching for the word "long" using /long.

Interpreting a Man Page

Just seeing the text isn't enough; you need to understand its structure and syntax. Man pages follow a standard format.

The most important sections are:

• NAME: The command name and a one-line description.
• SYNOPSIS: The command's syntax, showing how to structure it with options and arguments.
• DESCRIPTION: A detailed explanation of what the command does.
• OPTIONS: A list of all the flags (like -l or --all) that modify the command's behavior.
• EXAMPLES: Practical examples of how to use the command. This is often the most useful section!
• SEE ALSO: A list of related commands and man pages.

The SYNOPSIS section has its own special language. Understanding it is key to interpreting how to use any command correctly.

Man Page Sections and apropos

Man pages are organized into numbered sections. For the Linux+ exam, it's useful to know a few:

• 1: Executable programs or shell commands
• 5: File formats and conventions (e.g., man 5 passwd describes the /etc/passwd file)
• 8: System administration commands (usually for root)

Sometimes, a term exists in multiple sections. For instance, passwd is a command (section 1) and a file format (section 5). You can specify the section you want:

man 1 passwd  # Shows the man page for the passwd command
man 5 passwd  # Shows the man page for the /etc/passwd file format

What if you don't know the exact command name? You can search the man page names and descriptions using apropos (or man -k).

apropos "copy file"

This will list all man pages that have "copy" or "file" in their short description, helping you discover commands like cp, scp, and install.

2. The info Command: An Interactive Guide

While man is the universal standard from the old Unix days, the GNU Project (which created many of the tools in Linux, including bash) developed its own documentation system: info.

info documents are structured like a digital book with hyperlinked "nodes". They are often more tutorial-like and in-depth than man pages, especially for complex GNU utilities.

To see it in action, try this:

info ls

You'll notice it looks different from a man page. Here are the essential navigation keys for info:

• n: Go to the next node.
• p: Go to the previous node.
• u: Go up to the parent node.
• Tab: Move to the next hyperlink on the current page.
• Enter: Follow the selected hyperlink.
• q: Quit.

For a great example of info's power, look at the documentation for all the core utilities at once:

info coreutils

This brings you to a top-level menu. You can navigate into the "Individual utilities" node to find detailed information on ls, cp, mv, rm, and many others.

When to use man vs. info?

• Use man for a quick reference on nearly any command. It's your first stop.
• Use info when you want a deeper, more conceptual understanding of a GNU utility (like bash, sed, find, or anything in coreutils).

3. Quick Help and Shell Built-ins

Sometimes, even a man page is too much. For a quick reminder of a command's options, most commands support a --help flag.

ls --help
cp --help

This prints a short usage summary directly to your terminal. It's perfect when you know the command but just forgot a specific option.

Finally, some commands aren't separate programs. They are built directly into the shell (the command-line interpreter, bash in our case). Commands like cd, pwd, and echo are "shell built-ins".

You can check a command's type with the type command:

type ls    # Output will show ls is a file, e.g., /bin/ls
type cd    # Output will say "cd is a shell builtin"

Shell built-ins do not have their own man pages. To get help for them, you use the shell's own help command.

help cd

Conclusion

You now have a complete toolkit for finding documentation and help directly within your Linux system. This ability to "help yourself" is fundamental to becoming a proficient user and is heavily emphasized in the Linux+ exam.

Key Takeaways:

• man: The standard manual system. Use it first for almost any command. Navigate with q, /, and arrow keys. Interpret the SYNOPSIS using its special conventions.
• apropos: Searches man page descriptions to help you find commands when you don't know the exact name.
• info: A detailed, hyperlinked documentation system, ideal for in-depth learning about GNU tools.
• --help: A quick option summary for most commands.
• help: The specific command to get help for shell built-ins like cd.

In our next lesson, we will build on the concept of shell built-ins and take a closer look at the shell itself. We will explore what a shell is and distinguish between different shell types like bash, sh, and zsh.