Terminal basics · Lesson 4 of 34 · 6 minutes

Command history

Run a few safe commands, review history, and clear the display without resetting state.

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
Print a marker
Run echo training.
Hint & worked example
Write simple text to standard output. Prefer printf when exact formatting matters.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
echo training
```
Remember: Redirection can overwrite an existing file before the command runs.
2
Show history
Run history.
Hint & worked example
Review commands entered during this session. History is a navigation aid, not evidence that a command succeeded.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
history
```
Remember: Completion in this release checks command outcomes, not history strings alone.
3
Clear output
Run clear.
Hint & worked example
Clear visible terminal output without erasing files or earned progress.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
clear
```
Remember: Clearing the screen is not the same as resetting the lab.

Understand the pattern

History can help repeat safe commands, but it can also reveal pasted secrets in real shells.

echo: Write simple text to standard output. Prefer printf when exact formatting matters.
Redirection can overwrite an existing file before the command runs.
history: Review commands entered during this session. History is a navigation aid, not evidence that a command succeeded.
Completion in this release checks command outcomes, not history strings alone.
clear: Clear visible terminal output without erasing files or earned progress.
Clearing the screen is not the same as resetting the lab.

Worked example and expected result

$ echo training

training

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

$ history

   1  echo training

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

$ clear

(no output; exit 0)

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 “Command history”, which interpretation is safe?Completion in this release checks command outcomes, not history strings alone.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Manual pages 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