Nano and editing · Lesson 22 of 27 · 8 minutes

Nano incident template

Use an incident template to structure review notes.

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
Copy incident template
Run cp data/incident-template.md lab/incident.md.
Hint & worked example
Copy a file to a new location, leaving the original in place.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cp data/incident-template.md lab/incident.md
```
Remember: Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
2
Open incident note
Run nano lab/incident.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/incident.md
```
Save this example in the editor:
```
# Nano incident template
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Find evidence field
Run grep evidence lab/incident.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 evidence lab/incident.md
```
Remember: No matches is exit status 1, which is different from a malformed invocation.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

cp: Copy a file to a new location, leaving the original in place.
Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
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.

Worked example and expected result

$ cp data/incident-template.md lab/incident.md

(no output; exit 0)

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

$ nano lab/incident.md

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

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

$ Save the editor buffer

# Nano incident template
status=reviewed
evidence=recorded
rollback=ready

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

$ grep evidence lab/incident.md

evidence=recorded

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 incident template”, 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 incident template” 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 service note 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