Terminal basics · Lesson 32 of 34 · 8 minutes

Help before change

Build the habit of reading command guidance and current metadata first.

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
Review the simulator commands
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.
2
Read permission guidance
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
Inspect the target metadata
Run stat README.txt.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat README.txt
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Reading help and metadata before a change helps operators explain what they know before they change anything.

help: List the commands supported by this teaching simulator.
A familiar command may support fewer flags here than in a full shell.
man: Read a short built-in teaching reference for one supported command.
For real administration, check the installed command manual and version too.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ 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.

$ 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.

$ stat README.txt

Path: /home/learner/README.txt
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 148 bytes

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 “Help before change”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.For real administration, check the installed command manual and version too.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Terminal recovery sequence 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