Nano and editing · Lesson 20 of 27 · 8 minutes

Nano rollback note

Write rollback notes after reading evidence.

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 template
Run cat data/incident-template.md.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat data/incident-template.md
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Open rollback note
Run nano lab/rollback.md. Save a nonempty note using the worked example below. Required evidence: status=reviewed; evidence=recorded; rollback=ready.
Hint & worked example
Edit a virtual text file using the browser editor and explicitly save it.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
nano lab/rollback.md
```
Save this example in the editor:
```
# Nano rollback note
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Inspect rollback note
Run stat lab/rollback.md.
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 lab/rollback.md
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
nano: Edit a virtual text file using the browser editor and explicitly save it.
Opening the editor does not complete a write task. Save and verify the contents.
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

$ cat data/incident-template.md

summary:
evidence:
impact:
next action:
rollback:

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

$ nano lab/rollback.md

Opening simulated nano for /home/learner/lab/rollback.md. Save or cancel in the browser.

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

$ Save the editor buffer

# Nano rollback note
status=reviewed
evidence=recorded
rollback=ready

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

$ stat lab/rollback.md

Path: /home/learner/lab/rollback.md
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 70 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 “Nano rollback note”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Opening the editor does not complete a write task. Save and verify the contents.

Apply it elsewhere

Before adapting the nano workflow from “Nano rollback note” 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: Nano nginx review 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