Skip to content
Clairos Learn

Nano and editing · Lesson 1 of 27 · 10 minutes

Editing with nano

Open the simulated nano editor, save a text file, and verify your change.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated Linux lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Reading back changes is a simple habit that prevents confusion.

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.

stat
Inspect a file or directory metadata record, including ownership, permissions, and size.

Metadata and file contents answer different questions.

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/incident-notes.txt
Opening simulated nano for /home/learner/lab/incident-notes.txt. Save or cancel in the browser.

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

$ Save the editor buffer
# Editing with nano
status=reviewed
evidence=recorded
rollback=ready

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

$ cat lab/incident-notes.txt
# Editing with nano
status=reviewed
evidence=recorded
rollback=ready

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

$ stat lab/incident-notes.txt
Path: /home/learner/lab/incident-notes.txt
Type: file
Mode: -rw-r--r--
Owner: learner
Group: learners
Size: 69 bytes

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 with nano”, which interpretation is safe?

Apply it elsewhere

Before adapting the nano workflow from “Editing with nano” to another server, what should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Editing config notesTry 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

  1. 01Editing config notesCopy a system config into your lab, edit it safely, and compare the result.Practice
  2. 02Edit and verifyCreate a runbook, count its lines, and inspect metadata after saving.Practice
  3. 03Nano runbookCreate a small operational runbook in simulated nano.Practice