Nano and editing · Lesson 18 of 27 · 8 minutes

Editing checkpoint runbook

Create a final mini-runbook and verify it.

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 operator runbook
Run nano lab/operator-runbook.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/operator-runbook.md
```
Save this example in the editor:
```
# Editing checkpoint runbook
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
2
Search reviewed marker
Run grep reviewed lab/operator-runbook.md.
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 reviewed lab/operator-runbook.md
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Read runbook
Run cat lab/operator-runbook.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 lab/operator-runbook.md
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

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

Worked example and expected result

$ nano lab/operator-runbook.md

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

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

$ Save the editor buffer

# Editing checkpoint runbook
status=reviewed
evidence=recorded
rollback=ready

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

$ grep reviewed lab/operator-runbook.md

status=reviewed

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

$ cat lab/operator-runbook.md

# Editing checkpoint runbook
status=reviewed
evidence=recorded
rollback=ready

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 “Editing checkpoint runbook”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.No matches is exit status 1, which is different from a malformed invocation.

Apply it elsewhere

Before adapting the grep workflow from “Editing checkpoint runbook” 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 config copy 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