Linux › Module 2 › Lesson 3
Text Editors (nano, vim basics)
Edit config files and scripts with nano and vim basics
Opening
Linux is configured in text — not in a hidden Control Panel
You can copy, move, read, and delete files. That is still half of operations: most Linux settings are ordinary text files. sshd_config, crontab fragments, .bashrc, nginx site files, your own notes — all of them are bytes you can open in an editor. There is often no Settings GUI on a server. If you cannot save and quit nano or escape vim, you are locked out of the very files defenders change under pressure. This lesson is survival: two editors, explicit save/quit, and a rule about what you are allowed to edit.
1. Why configs are text (and why that is a gift)
A text config can be copied, hashed, diffed, grepped, and checked into version control. Binary "control panel" blobs cannot. When an incident responder asks "what changed?", the answer is often a line in /etc — but you will not practice by editing /etc yet. You will practice on a file in $HOME so a typo cannot break SSH on a machine you still need.
Because configs are text, the editor is a security tool. A missing newline, a commented-out directive, or a pasted command from a random blog can disable authentication. Read with cat/less first (last lesson). Then edit. Then re-read. That loop is more important than memorizing twenty vim motions.
2. nano: the beginner on-ramp — save and quit for real
nano file.txt opens the file (creating it if needed). The caret ^ on the cheat sheet means Ctrl. Ctrl+O writes Out (save): nano asks for the filename, you press Enter. Ctrl+X exits. If you changed the buffer, nano asks whether to save — that prompt is your last chance. Ctrl+K cuts a line; Ctrl+U pastes it. You can always see the shortcuts; that is why nano is the first editor to trust on a new VM.
Open only paths you own: nano "$HOME/cyberlium-lab/notes.txt". sudo nano /etc/hosts is a later, careful skill on machines you administer — not a first-week reflex. Editing system files without knowing the service is how labs lose SSH.
3. vim: modal editing so you are not trapped
vim (and classic vi) start in Normal mode. Keys are commands, not letters. Press i for Insert mode, then type. Press Esc to return to Normal. Save and quit with :wq (write, then quit). Discard with :q!. If you are stuck in a sea of tildes, you are probably in Normal mode hammering keys — Esc, then :q! if you did not mean to edit.
vim still matters because minimal servers and rescue environments often have vi when nano is missing. You do not need to be fast. You need an exit. Five minutes of Esc / i / :wq / :q! prevents the meme of rebooting a VM because you could not leave the editor.
Minimum vim kit (say it once, then practice it):
i
Insert mode — now typing writes text into the file.
Esc
Back to Normal mode — commands work again.
:wq
Write (save) and quit. Typed in Normal mode, then Enter.
:q!
Quit and throw away unsaved changes. Your escape hatch.
4. Wrong vs right: "just fix SSH real quick"
Failure mode — a blog says the SSH banner is in a config and you should "nano it as root":
Wrong
sudo nano /etc/ssh/sshd_config on a machine you barely understand, paste a block from the internet, Ctrl+X without saving on purpose, or freeze in vim and reboot. Worse: chmod 777 / so the editor "can write anywhere." You can lock yourself out or wide-open the box. You also never learned save/quit.
Right
Practice on $HOME/cyberlium-lab/editor-practice.txt. Open with nano, type a sentence, Ctrl+O, Enter, Ctrl+X. Re-open with vim, press i, add a line, Esc, :wq. Confirm with cat. Leave /etc alone until you have a snapshot and a reason. Never rm -rf / and never chmod 777 / to make an editor cooperate.
5. Practical: save and quit on a file you own
YOUR VM or WSL only. Create the file in your home lab folder. If nano or vim is missing, install is a later lesson — use whichever editor exists, but still practice an explicit save and an explicit quit.
Safe editor drill (your home lab folder only)
whoami pwd mkdir -p "$HOME/cyberlium-lab" cd "$HOME/cyberlium-lab" # nano: Ctrl+O then Enter to save, Ctrl+X to quit nano editor-practice.txt # Confirm the text landed cat editor-practice.txt ls -la editor-practice.txt # vim: i to type, Esc, then :wq (or :q! to abort) # vim editor-practice.txt # NEVER edit / as a shortcut, and NEVER: # rm -rf / # chmod 777 /
Mission: one saved file, two exits
1) nano ~/cyberlium-lab/editor-practice.txt — write one sentence about why configs are text. Save (Ctrl+O) and quit (Ctrl+X). 2) cat the file to prove it persisted. 3) Open the same file in vim (or vi). Enter insert, add a second line, Esc, :wq. If you panic, Esc then :q! and try again. 4) Say: "I edit files I own in $HOME before I ever touch /etc."
Stuck? Ask Cyberlium AI Mentor
If vim swallowed your keyboard, ask Cyberlium AI Mentor for a hint — not a 50-command cheat sheet. Try: "Hint only: I see tildes and letters I type do not appear; how do I get to Insert, then how do I :q! safely?"
File operations taught you to copy and delete; editors teach you to change text in place. Configs are files, nano is the labeled steering wheel, vim is the editor that exists when nothing else does, and $HOME is where you practice. Next up — Lab — Terminal Practice — you will chain navigation, file ops, and an editor into one project folder under ~/cyberlium-lab.
Knowledge Check
APPLY: You opened nano notes.txt, typed a paragraph, and closed the window with the GUI X button. cat notes.txt is empty or missing. What most likely failed?
Multiple choice
Knowledge Check
APPLY: vim is open on a lab file. Keys you type move the cursor or beep; no letters appear. You want to leave WITHOUT saving. What sequence?
Multiple choice
Knowledge Check
APPLY: True or False: Because server configs live as text under /etc, the fastest way to learn nano is to edit sshd_config on day one without a VM snapshot.
True or False