Nano and editing · Lesson 4 of 27 · 9 minutes

Nano runbook

Create a small operational runbook in simulated nano.

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 lab
Run mkdir -p lab.
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mkdir -p lab
```
Remember: Creating a folder does not change the current directory.
2
Edit runbook
Run nano lab/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/runbook.md
```
Save this example in the editor:
```
# Nano runbook
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Read runbook
Run cat lab/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/runbook.md
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Written runbooks lower mistakes during stressful operations.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
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.
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

$ mkdir -p lab

(no output; exit 0)

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

$ nano lab/runbook.md

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

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

$ Save the editor buffer

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

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

$ cat lab/runbook.md

# Nano 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 “Nano runbook”, which interpretation is safe?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.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the nano workflow from “Nano runbook” 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 SSH 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