Nano and editing · Lesson 12 of 27 · 9 minutes

Nano incident timeline

Write a timeline and compare it with SSH journal entries.

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
Edit timeline
Run nano lab/timeline.txt. 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/timeline.txt
```
Save this example in the editor:
```
# Nano incident timeline
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
2
Read SSH journal
Run journalctl -u ssh.
Hint & worked example
Read the training journal by unit or a bounded line window.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u ssh
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.
3
Read timeline
Run cat lab/timeline.txt.
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/timeline.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.

Understand the pattern

Incident reviews depend on ordered events.

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.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.
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/timeline.txt

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

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

$ Save the editor buffer

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

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

$ journalctl -u ssh

May 26 08:14:02 clairos-learn sshd[104]: publickey accepted for learner
May 26 08:18:33 clairos-learn sshd[118]: password authentication refused
May 26 08:21:44 clairos-learn sshd[141]: root login refused by policy

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

$ cat lab/timeline.txt

# Nano incident timeline
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 incident timeline”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.A relevant unit and time range are more useful than an unfiltered wall of logs.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the journalctl workflow from “Nano incident timeline” 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 checklist 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