01 / Foundation
Understand your Linux system
Build a mental model of the kernel, distribution, terminal, shell, and filesystem before memorizing commands.
The BashQuest learning library
Build the mental model, practice in the terminal, and prove your skills on a real system. Follow a connected path from your first command to everyday Linux operations.
New to Linux? Start with chapters 1–4 and their quests, then set up a disposable machine. Already use the terminal? Find gaps with the knowledge checks, then try the Boss Challenges. Preparing for operations work? Complete the real-system labs and keep your verification notes.
Read → predict the result → run the command → explain the result without hints. Revisit a completed module after a day and again after a week.
01 / Build understanding
01 / Foundation
Build a mental model of the kernel, distribution, terminal, shell, and filesystem before memorizing commands.
02 / Foundation
Create, copy, rename, remove, and link files while understanding what each operation changes.
03 / Foundation
Use standard input, standard output, and pipelines to turn small commands into useful workflows.
04 / Foundation
Understand permissions as access rules, not magic numbers.
05 / Administration
Use privilege and package managers deliberately, with a recovery plan.
06 / Administration
Distinguish capacity, filesystem usage, mounts, memory pressure, and device layout.
07 / Administration
Find the right process, inspect it, and choose a proportionate intervention.
08 / Administration
Separate interface, routing, DNS, transport, TLS, and application failures.
09 / Administration
Choose between a live filesystem search, a cached index, and searching inside files.
10 / Administration
Understand running state, startup policy, logs, and the boot sequence.
11 / Administration
Make small, reversible changes and validate their effect.
12 / Automation
Move from command sequences to programs with inputs, decisions, and observable failures.
13 / Automation
Choose a tool that understands the input structure and validate the output.
14 / Automation
Understand variable scope, startup files, command lookup, and reproducibility.
15 / Operations
Treat a successful restore as the proof of a backup.
16 / Operations
Understand users, groups, SSH trust, and least privilege.
17 / Operations
Combine version control, containers, and operational checks without confusing them with isolation guarantees.
No matching topics. Try a broader term such as files, shell, or network.
02 / Find your next exercise
Search quests by title, command, or objective. Each reference includes an explanation and a direct terminal launch.
150 quests
03 / Transfer your skills
The browser terminal is a JavaScript simulator. It models selected commands; it does not run a Linux kernel, contact remote hosts, install real packages, or implement all of Bash. These labs run in your own disposable Linux environment. They are self-assessed and do not award quest XP.
Create a disposable Linux environment and learn what the browser cannot simulate.
cat /etc/os-release
uname -r
whoami
printf "%s\n" "$SHELL" "$HOME"
mkdir -p ~/linux-lab
cd ~/linux-lab
pwdA short system inventory and a working snapshot or other recovery method. Explain terminal versus shell versus kernel without looking it up.
Revert the VM snapshot. Keep any notes you need outside the disposable guest before reverting.
Create data, back it up, restore it somewhere new, and compare every recovered file.
lab_dir=$(mktemp -d)
cd "$lab_dir"
mkdir source restore
printf "Linux practice\n" > source/notes.txt
cp source/notes.txt source/second.txt
tar -czf backup.tar.gz source
tar -tzf backup.tar.gz
tar -xzf backup.tar.gz -C restore
diff -r source restore/source
sha256sum backup.tar.gzThe archive listing, a clean comparison, a deliberately detected difference, and a written recovery procedure.
Keep the unique workspace until you finish reviewing it. It can be removed later after confirming its exact path; no system files were changed.
Write and test a script with quoted arguments, a clear error path, and meaningful exit statuses.
#!/usr/bin/env bash
if [ "$#" -ne 1 ]; then
printf "Usage: report.sh DIRECTORY\n" >&2
exit 2
fi
if [ ! -d "$1" ]; then
printf "Not a directory: %s\n" "$1" >&2
exit 1
fi
find "$1" -type fRecord all three test cases, actual exit codes, stdout, and stderr. Add a test for an empty directory.
The script only inspects files. Edit or remove the script within your practice directory to start again.
Distinguish a missing listener, a stopped service, and an application error using evidence.
systemctl status nginx
journalctl -u nginx -b --no-pager -n 30
ss -lnt
curl -I http://127.0.0.1
systemctl is-enabled nginx
systemctl is-active nginxBefore, during, and after observations showing why the application was unreachable. Confirm the restored HTTP response, not just the service status.
Start nginx again or revert the snapshot. If the distribution does not use systemd, use a systemd-based disposable VM for this exercise.
Predict permission effects, reproduce them without root, and explain least privilege.
lab_dir=$(mktemp -d)
cd "$lab_dir"
printf "private\n" > note.txt
chmod 000 note.txt
cat note.txt
chmod 600 note.txt
cat note.txt
ls -l note.txt
id
groupsA permission prediction table, the observed denial and recovery, and a least-privilege explanation for both proposed files.
Restore mode 600 on note.txt. All changes are confined to the temporary workspace.
You should be able to navigate, manipulate data, diagnose common failures, write small scripts, and verify routine changes. Kernel development, advanced storage, SELinux/AppArmor policies, high availability, and production architecture require further specialist practice. Check the manuals installed on your system for its exact behavior.
Return to your quest dashboard →