Terminal basics · Lesson 5 of 34 · 6 minutes

Manual pages

Use simulated manual pages to learn command intent before running tools.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read ls help
Run man ls.
Hint & worked example
Read a short built-in teaching reference for one supported command.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
man ls
```
Remember: For real administration, check the installed command manual and version too.
2
Read chmod help
Run man chmod.
Hint & worked example
Read a short built-in teaching reference for one supported command.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
man chmod
```
Remember: For real administration, check the installed command manual and version too.
3
Show simulator help
Run help.
Hint & worked example
List the commands supported by this teaching simulator.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
help
```
Remember: A familiar command may support fewer flags here than in a full shell.

Understand the pattern

Real terminals reward operators who read before changing state.

man: Read a short built-in teaching reference for one supported command.
For real administration, check the installed command manual and version too.
help: List the commands supported by this teaching simulator.
A familiar command may support fewer flags here than in a full shell.

Worked example and expected result

$ man ls

LS(1)
NAME
  ls - list simulated directory contents
SYNOPSIS
  ls [-la] [path]
NOTE
  Use -a for hidden dotfiles and -l for metadata.

Exit status: 0. The command completed successfully in the training fixture.

$ man chmod

CHMOD(1)
NAME
  chmod - change simulated permission modes
SYNOPSIS
  chmod <mode> <path>
NOTE
  In this lab, chmod changes metadata only.

Exit status: 0. The command completed successfully in the training fixture.

$ help

Simulated commands: help, pwd, ls, cd, man, which, type, env, uname, hostname, date, echo, printf, mkdir, touch, nano, cat, less, head, tail, grep, awk, sed, cut, tr, tee, xargs, wc, sort, uniq, nl, comm, diff, sha256sum, find, file, realpath, mktemp, basename, dirname, readlink, test, tar, ln, cp, mv, rm, chmod, chown, chgrp, stat, whoami, id, groups, ps, top, kill, pgrep, lsof, systemctl, journalctl, nginx, sudo, ufw, ss, ip, mount, lsblk, crontab, logrotate, launchctl, plutil, apt, dpkg, brew, ssh, scp, ssh-keygen, df, du, free, uptime, history, clear, reset.
This terminal is simulated. Commands can only change the training filesystem in your browser.

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Manual pages”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.For real administration, check the installed command manual and version too.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the man workflow from “Manual pages” to another server, what should you do?Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Command locations Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual