Nano and editing · Lesson 17 of 27 · 8 minutes

Nano package note

Inspect package metadata and record a review.

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
List installed packages
Run apt list --installed.
Hint & worked example
Inspect a fixed training package inventory. The simulator cannot install or upgrade your computer.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
apt list --installed
```
Remember: Candidate, installed, and repository versions answer different questions.
2
Write package note
Run nano lab/package-review.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/package-review.txt
```
Save this example in the editor:
```
# Nano package note
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Read package note
Run cat lab/package-review.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/package-review.txt
```
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.

apt: Inspect a fixed training package inventory. The simulator cannot install or upgrade your computer.
Candidate, installed, and repository versions answer different questions.
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

$ apt list --installed

fake-nginx/learn 1.0 installed
fake-openssh/learn 9.9 installed
coreutils/learn 9.5 installed

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

$ nano lab/package-review.txt

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

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

$ Save the editor buffer

# Nano package note
status=reviewed
evidence=recorded
rollback=ready

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

$ cat lab/package-review.txt

# Nano package note
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 package note”, 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 package note” 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: Editing checkpoint runbook 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