File Operations (cp, mv, rm, cat)

cat prints a file's entire contents to the terminal. It is perfect for short notes and for /etc/os-release on your own box. It is a poor pager for a 4,000-line log: the interesting error scrolls off the screen. less shows one screen at a time (space to page, / to search, q to quit) without modifying the file. head prints the first lines (head -n 20 file) so you can sample a log without drowning.

tail shows the end of a file — usually the newest lines if the file only appends. head and tail together are how you learn a format and then check the latest events. Reading is the safe default. Before cp, mv, or rm, cat or less the file (or ls -la the directory) so you are acting on the object you think you are.

Defenders live in read mode: you cannot copy evidence you have not identified, and you must not delete it. In the lab, that habit looks like: create a practice note, cat it, then mutate a copy — not the only original you care about.

cp makes a second object. cp notes.txt notes-backup.txt leaves the original. Directories need recursion: cp -r project project-copy copies the tree. Prefer copying into a destination you just listed with ls. If the destination path already exists as a file, many setups overwrite without a dramatic warning — another reason to ls first and to keep practice under $HOME/cyberlium-lab.

mv does not copy; it relocates the same inode when it can (same filesystem). In the same directory, mv draft.txt final.txt is a rename. Across directories, mv report.txt ~/Documents/ is a move. After mv, the old path is gone. That is the whole point — and the whole risk if pwd was wrong. Quote paths with spaces: mv "my notes.txt" "final notes.txt".

A safe habit: cp first when you might need the original, then mv the copy to a new name, then rm only the extra when you are sure. That sequence turns "I hope this rename is right" into a reversible drill.

rm removes a file. There is typically no Trash. rm -r directory deletes the directory and everything inside it. The flags -r (recursive) and -f (force, ignore missing files and many prompts) together are how people turn a typo into a wiped tree. rm -rf / aims at the filesystem root. On a system you should never run it. On a VM it is still a terrible habit: it trains your fingers to type catastrophe.

Wildcards make this sharper. rm *.log deletes every matching name in the current directory. rm * in the wrong pwd is a career story. Prefer: cd to the practice folder, ls the match (ls *.txt), then rm a named file you just created. Interactive rm -i asks before each delete on some systems — useful on boxes you care about. Never chmod 777 / to "make delete work."

If you need to clean a lab folder, delete named practice files one at a time, or remove a single directory you created (rm -r "$HOME/cyberlium-lab/file-ops/scratch") after pwd confirms you are not at /. Specificity is the safety feature.

Only under $HOME/cyberlium-lab on YOUR VM or WSL. If a command mentions / as a delete target, stop. You are not cleaning the OS. You are learning reversible file hygiene.

whoami
cd ~
pwd
mkdir -p "$HOME/cyberlium-lab/file-ops"
cd "$HOME/cyberlium-lab/file-ops"
pwd

echo "cyberlium file-ops practice" > notes.txt
cat notes.txt
head -n 5 notes.txt

less notes.txt     # press q to quit if you open it

Copy then rename (mv) — original preserved until you choose

cp notes.txt notes-backup.txt
ls -la
mv notes-backup.txt notes-renamed.txt
ls -la

rm notes-renamed.txt
ls -la

tail -n 1 notes.txt

rm -rf /
rm -rf *
chmod 777 /
rm with a path you have not verified via pwd and ls

Navigation taught you where you are; this lesson taught you how objects move and why rm has no undo. You practiced cat/less/head before mutation, cp for copies, mv for rename/move, and a single named rm in $HOME. Next up — Text Editors (nano, vim basics) — because configs and notes are text, and you will need to change them without a GUI.