Nano and editing · Lesson 26 of 27 · 8 minutes

Nano recovery note

Write a rollback-oriented note and verify every required field.

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
Write the recovery note
Run nano lab/recovery-note.txt. Type exactly: before=443, change=8443, rollback=443 on separate lines, then save with Ctrl+O. Save a nonempty note using the worked example below. Required evidence: before=443; change=8443; rollback=443.
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/recovery-note.txt
```
Save this example in the editor:
```
before=443
change=8443
rollback=443
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
2
Verify the rollback line
Run grep rollback lab/recovery-note.txt.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep rollback lab/recovery-note.txt
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Inspect the saved file
Run stat lab/recovery-note.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 lab/recovery-note.txt
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Recording recovery steps before an operational change helps operators explain what they know before they change anything.

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.
grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.
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

$ nano lab/recovery-note.txt

Opening simulated nano for /home/learner/lab/recovery-note.txt. Save or cancel in the browser.

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

$ Save the editor buffer

before=443
change=8443
rollback=443

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

$ grep rollback lab/recovery-note.txt

rollback=443

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

$ stat lab/recovery-note.txt

Path: /home/learner/lab/recovery-note.txt
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 36 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 recovery note”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.No matches is exit status 1, which is different from a malformed invocation.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the grep workflow from “Nano recovery note” 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: Nano editing bridge 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