Nano and editing · Lesson 16 of 27 · 8 minutes

Nano network note

Pair socket inspection with an operator note.

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
Inspect sockets
Run ss -tulpn.
Hint & worked example
Inspect simulated listening sockets and connection information.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ss -tulpn
```
Remember: A listening socket is not proof of correct application responses or external reachability.
2
Write network note
Run nano lab/network-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/network-review.txt
```
Save this example in the editor:
```
# Nano network note
status=reviewed
evidence=recorded
rollback=ready
```
Remember: Opening the editor does not complete a write task. Save and verify the contents.
3
Read network note
Run cat lab/network-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/network-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.

ss: Inspect simulated listening sockets and connection information.
A listening socket is not proof of correct application responses or external reachability.
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

$ ss -tulpn

Netid State  Local Address:Port  Process
udp   UNCONN 0.0.0.0:68          lab-dhcp
tcp   LISTEN 0.0.0.0:22          sshd
tcp   LISTEN 0.0.0.0:80          nginx
tcp   LISTEN 0.0.0.0:443         nginx

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

$ nano lab/network-review.txt

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

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

$ Save the editor buffer

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

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

$ cat lab/network-review.txt

# Nano network 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 network note”, which interpretation is safe?Opening the editor does not complete a write task. Save and verify the contents.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the nano workflow from “Nano network note” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Nano package 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