RHCSA V10

Part of RHCSA V10. This matters more than it looks on the exam — you get zero internet access during RHCSA, so man and --help are the only references you have.


man — the primary reference

man ls              # manual page for the ls command
man -k partition     # keyword search across all man pages (same as apropos)
apropos partition    # identical to man -k
whatis ls            # one-line summary of what a command is

Man page sections

Man pages are organized into numbered sections. The same name can exist in multiple sections meaning different things — passwd is both a command and a file format:

SectionCovers
1User commands
2System calls (kernel functions)
3Library calls (C library functions)
4Special files (usually in /dev)
5File formats and conventions
6Games
7Miscellaneous (protocols, conventions, overviews)
8System administration commands (mostly root-only)
man passwd            # section 1 by default — the passwd COMMAND
man 5 passwd           # explicitly section 5 — the /etc/passwd FILE FORMAT
man -a passwd          # walk through every section that has an entry

Knowing to reach for man 5 fstab instead of man fstab (which doesn’t exist — fstab isn’t a command) is a real exam-relevant skill.

Man pages open in a pager (less under the hood):

KeyAction
Space / fPage down
bPage up
/termSearch forward for term
nNext search match
NPrevious search match
gJump to top
GJump to bottom
qQuit

Man page structure

Every man page follows roughly the same skeleton — knowing the skeleton means you can skim straight to what you need instead of reading top to bottom:

NAME          — one-line description
SYNOPSIS      — exact command syntax, [optional] vs required args
DESCRIPTION   — full explanation
OPTIONS       — every flag, explained
EXAMPLES      — sample invocations (not every page has this)
FILES         — related config/data files
SEE ALSO      — related man pages

—help — faster, shallower

Almost every command supports command --help (or -h) for a quick flag summary printed straight to the terminal — no pager, no full explanation. Good for “what was that flag called again” when you already know the command.

tar --help
systemctl --help

info — GNU’s deeper alternative

Some GNU tools ship more detailed Texinfo documentation than their man page, browsable as a menu-driven hypertext document:

info coreutils
KeyAction
SpaceNext page
EnterFollow a menu link under the cursor
uUp one menu level
qQuit

In practice man covers the vast majority of what you need day to day; info is worth knowing exists for the handful of tools (like coreutils, bash itself) that document themselves more thoroughly there.


Local package documentation

ls /usr/share/doc/<package-name>/     # READMEs, changelogs, example configs shipped with a package
rpm -qd httpd                          # list documentation files owned by a specific package
rpm -ql httpd                          # list ALL files owned by a package (not just docs)

RHEL Lightspeed — the AI-assisted command-line assistant (new in RHEL 10)

Not usable during the offline exam (it requires internet access and a registered subscription), but worth knowing about as the newest addition to RHEL’s “getting help” toolkit, and genuinely useful on the job. RHEL Lightspeed is Red Hat’s AI layer over RHEL — the piece relevant here is its command-line assistant, which lets you ask an English-language question straight from the terminal and get back an explanation, a suggested command, or help interpreting output you paste in. Under the hood it calls an externally-hosted LLM (IBM’s watsonx/Granite), trained on Red Hat’s own documentation and knowledgebase articles — it does not inspect your system directly; it only ever sees what you explicitly type or pipe to it.

sudo dnf install command-line-assistant   # one-time setup; needs a registered subscription
c chat "how do I list running services?"          # ask a plain-English question
c chat --interactive                                # multi-turn conversation instead of one-off questions

Where it gets genuinely useful is piping real output into it for interpretation, rather than just asking abstract questions:

journalctl -u httpd --since "1 hour ago" | c chat "what could be causing errors in these logs?"
sudo systemctl status httpd | c chat "check the logs, help me fix the issue"
c chat -a /var/log/boot.log "why did the last boot take so long?"   # -a/--attachment: send a whole file

Treat every answer the same way you’d treat an answer from a stranger on a forum: plausible, usually helpful, but always verify before running a suggested command — this isn’t a formality, it’s Red Hat’s own explicit guidance, since the assistant can suggest something incomplete or subtly wrong. It’s a research aid that sits alongside man/--help/info, not a replacement for actually understanding what a command does before you run it.


Red Hat’s own documentation (outside the exam)

Not usable during the offline exam, but the real-world answer once you’re on the job:

  • access.redhat.com/documentation — official product docs per RHEL version
  • Red Hat Customer Portal — Knowledgebase articles, especially for weird specific error messages
  • Red Hat Bugzilla — tracked bugs, useful when something looks like a known issue rather than a config mistake
↑ Back to Red Hat Certified System Administrator (RHCSA) V10