Reading the Manual (man pages)
Nobody memorises every command and flag, not even senior engineers. What separates them is knowing how to look it up fast, right in the terminal, without reaching for a browser. On a Unix system the answer is almost always one command away, because nearly every tool ships its own built-in manual: the man page (short for manual).
Think of man as the help desk that's always open: you walk up, name the command you're
stuck on, and it hands you the full reference. In five short steps you'll open a page,
search inside it, find a command by what it does, get a one-line summary, and learn how
the manual is organised.
5 mini lessons
0 of 5 done- Open a manual page
- Search inside a page
- Find a command by what it does
- Get the one-line summary
- Explain the sections
Interview prep
Knowing how to read the manual is what lets you pick up any command on the job; interviewers notice when you reach for man instead of guessing.
You're on a server with no internet and don't remember a command's flags. What do you do?
Read its manual in place: man <cmd> opens the page, and man <cmd> | grep <keyword> jumps straight to the flag I need. If I don't even know the command's name, apropos <keyword> (a.k.a. man -k) searches every manual's summary by topic, and whatis <cmd> gives the one-line reminder. The section number in ls (1) tells me which manual section the page lives in — handy when a name exists in several (e.g. passwd (1) the command vs passwd (5) the file).