Terminal basics · Lesson 14 of 34 · 6 minutes

Reset the lab

See the difference between local changes and resetting the lab environment.

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
Create marker
Run touch reset-test.txt.
Hint & worked example
Create an empty file when absent, or update timestamps without truncating an existing file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
touch reset-test.txt
```
Remember: touch is not a way to empty a file that already has content.
2
Reset simulator
Run reset.
Hint & worked example
Reset the current virtual environment. It never resets the operating system running your browser.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
reset
```
Remember: Save a relevant result before discarding scratch work.
3
List home
Run ls /home/learner.
Hint & worked example
List directory entries; -a includes hidden names and -l adds ownership and permission detail.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ls /home/learner
```
Remember: A listing is not proof that you can read or modify every listed file.

Understand the pattern

Resettable training lowers the cost of experimenting.

touch: Create an empty file when absent, or update timestamps without truncating an existing file.
touch is not a way to empty a file that already has content.
reset: Reset the current virtual environment. It never resets the operating system running your browser.
Save a relevant result before discarding scratch work.
ls: List directory entries; -a includes hidden names and -l adds ownership and permission detail.
A listing is not proof that you can read or modify every listed file.

Worked example and expected result

$ touch reset-test.txt

(no output; exit 0)

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

$ reset

Virtual filesystem reset. Lesson audit retained; earned progress is unchanged.

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

$ ls /home/learner

archive  backups  data  lab  notes  projects  README.txt  restore  scripts

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 “Reset the lab”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Save a relevant result before discarding scratch work.

Apply it elsewhere

Before adapting the reset workflow from “Reset the lab” 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: Printf formatting 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