man, one lesson per page
Twenty-nine lessons for reading Linux manual pages: the section numbers and why one name owns several pages, the NAME to SEE ALSO spine every page shares, how to parse a SYNOPSIS like a grammar (bold you type, italic you replace, brackets optional, pipes exclusive), man -k and the full-text -K search, the search order that decides which page wins, the less pager keys that do the real reading (slash to search, n and N to walk hits, g and G to jump, h for the built-in summary), SEE ALSO trails, man -w to find the file behind a page, MANPATH and locale pages, and the one habit that answers most questions without a search engine.
A diagram, the map, and one thing to try this week. That's a page.
man, one lesson per page
Twenty-nine lessons for reading Linux manual pages: the section numbers and why one name owns several pages, the NAME to SEE ALSO spine every page shares, how to parse a SYNOPSIS like a grammar (bold you type, italic you replace, brackets optional, pipes exclusive), man -k and the full-text -K search, the search order that decides which page wins, the less pager keys that do the real reading (slash to search, n and N to walk hits, g and G to jump, h for the built-in summary), SEE ALSO trails, man -w to find the file behind a page, MANPATH and locale pages, and the one habit that answers most questions without a search engine.
Set in Space Grotesk, Inter and JetBrains Mono (SIL Open Font License).
Every fact in this book is as the official sources state it, fetched and read during this build: the man(1) man page, the man-pages(7) conventions page and the less(1) man page hosted at man7.org (the Linux man-pages project), and the Debian man-db man(1) page at manpages.debian.org. The man7.org project home page was read for orientation only and no facts are sourced from it. man-db-specific defaults (the search order, the pager fallback) are labelled as that project states them. Demand evidence from live beginner threads, reconfirmed at dispatch; no facts are sourced from Reddit or StackExchange. An independent guide, not affiliated with or endorsed by the Linux man-pages project or the Debian Project.
Your purchase is for personal use only. You do not have redistribution rights: please do not share, resell, or republish this book or its pages.
© 2026 Steve Hodgkiss. All rights reserved. Personal use only; no redistribution rights.
Edition 1.0 · stevehodgkiss.net
Contents
The page itself
The shared spine from NAME to SEE ALSO: the one-line description, the SYNOPSIS grammar of bold, italic, brackets, pipes and ellipses, terminal rendering, DESCRIPTION versus OPTIONS, and the quiet ENVIRONMENT and FILES sections.
- 01One page, one spine
- 02Read the SYNOPSIS
Per man(1) (man7.org, Linux man-pages project): man is an interface to the system reference manuals; each page argument is normally the name of a program, utility or function; the manual page associated with each argument is then found and displayed; conventional section names include NAME, SYNOPSIS, CONFIGURATION, DESCRIPTION, OPTIONS, EXIT STATUS, RETURN VALUE, ERRORS, ENVIRONMENT, FILES, VERSIONS, STANDARDS, NOTES, BUGS, EXAMPLE, AUTHORS, and SEE ALSO.
One page, one spine
Every manual page is built from the same set of sections, in the same conventional order: NAME, SYNOPSIS, DESCRIPTION, then the reference matter.
The conventions list in man(1) runs NAME, SYNOPSIS, CONFIGURATION, DESCRIPTION, OPTIONS, EXIT STATUS, RETURN VALUE, ERRORS, ENVIRONMENT, FILES, VERSIONS, STANDARDS, NOTES, BUGS, EXAMPLE, AUTHORS, SEE ALSO. Not every page carries every section.
Learn the spine once and you can open any page on any machine.
Open one page you use weekly and name its sections aloud before you read them this week.
Per man(1) (man7.org), SYNOPSIS conventions: bold text - type exactly as shown; italic text - replace with appropriate argument; [-abc] any or all arguments within [ ] are optional; -a|-b options delimited by | cannot be used together; argument ... argument is repeatable; [expression] ... the entire expression within [ ] is repeatable.
Read the SYNOPSIS
The SYNOPSIS is a pattern that matches every invocation, not an example to copy. man(1) gives the reading rules.
Bold you type exactly. Italic you replace with your own argument. Square brackets mark optional parts. A pipe means the two options cannot be used together. A trailing ellipsis means the argument repeats.
Parse the synopsis before the description and the description reads faster.
Take one SYNOPSIS this week, draw brackets around the optional parts, and write the plainest command that fits it.
Per man(1) (man7.org), the section table: 1 Executable programs or shell commands; 2 System calls (functions provided by the kernel); 3 Library calls (functions within program libraries); 4 Special files (usually found in /dev); 5 File formats and conventions e.g. /etc/passwd; 6 Games; 7 Miscellaneous including macro packages and conventions; 8 System administration commands (usually only for root); 9 Kernel routines [Non standard].
Nine manual sections
The manual is nine sections, each a shelf for a kind of thing: 1 programs and shell commands, 2 system calls, 3 library calls, 4 special files in /dev, 5 file formats, 6 games, 7 miscellaneous, 8 admin commands, 9 kernel routines.
The number in ls(1) is an address, not a version. Everyone meets 1, 5 and 8 first.
Hold the map of nine and no page reference is mysterious.
Recite the nine sections once a day this week until 5 means file format without thinking.
Per man(1) (man7.org): man -k or --apropos is approximately equivalent to apropos, it searches the short manual page descriptions for keywords and displays any matches; man -f or --whatis is approximately equivalent to whatis.
Search by keyword
You do not need the page's name, only a word from its world. man -k searches the short descriptions and prints every match.
It is approximately equivalent to apropos, per man(1). Search partition, archive, socket, and the manual answers with candidate pages.
Start every unknown task with one -k query; it costs seconds.
Before your next search engine trip, try man -k with the same keywords this week and compare what comes back.
Per less(1) (man7.org): SPACE or ^V or f or ^F scrolls forward N lines, default one window; b or ^B or ESC-v scrolls backward N lines, default one window; ENTER or RETURN or ^N or e or ^E or j or ^J scrolls forward N lines, default 1; q or Q or :q or :Q or ZZ exits less.
Space, b, q
Three keys carry a whole session: SPACE forward one window, b backward one window, q exit.
less(1) lists them among the movement commands: SPACE or ^V or f or ^F forward, b or ^B or ESC-v back, q or Q or ZZ out. Enter jogs forward a single line.
If you only ever learn three keys, learn these.
Read one full page this week using nothing but space, b and q, and feel the page arrive in windows.
Per man(1), man-pages(7) and less(1) (man7.org, Linux man-pages project) and man-db man(1) (manpages.debian.org): the sections, the SYNOPSIS conventions, the search order, the -k and -K searches, the pager keys and the file locations, all as documented on those pages and practised across this book.
One habit to keep
The whole book is one habit: ask the manual first. Open with man and the name, search inside with the pager's slash, follow SEE ALSO when the page runs out.
Every technique on these pages serves that loop. Run it daily and the manual stops being a last resort and becomes the shortest path.
Twenty-nine lessons, one reflex: the answer is usually already installed.
Resolve one real question entirely inside the manual this week, search engine untouched, and notice how fast it actually was.