Run mkdir lab, then nano lab/runbook.txt.
mkdir labnano lab/runbook.txt
Mission 15
Edit and verify
Create a runbook, count its lines, and inspect metadata after saving.
Nano and editingnanowcstatcat
Lesson 15 of 360
0/360 lessons
0/17 missions
Nano and editing · 9 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
9 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
After saving, run wc -l lab/runbook.txt.
wc -l lab/runbook.txt
Run stat lab/runbook.txt.
stat lab/runbook.txt
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Build a readback habit after each file change.
Save a few short lines so wc has something to count.
Verification catches wrong paths, failed saves, and stale assumptions.
- Trusting an edit without reading it back.
- Checking the wrong filename.
Reference
Commands in this lesson.
nano <file>
Open a simulated nano editor.
cat <file>
Print text file contents.
wc [-l] <file>
Count lines, words, and characters.
stat <path>
Show lab file details.