How to learn Linux by playing (without breaking your computer)
A terminal that answers instantly, missions that are graded on a server, and a habit loop that survives a busy week.
The commands that show up in every interview, every server and every “it works on my machine” story.
You do not need three hundred commands. You need a dozen you can type without thinking, and the confidence that the rest are one man page away.
pwd # where am I?
ls -lah # what is here, with sizes and hidden files?
cd /var/log # go there
cat app.log
tail -n 50 -f app.log # follow a live log
less /etc/nginx/nginx.conf
grep -rn "timeout" /etc/nginx
find / -type f -size +100M 2>/dev/null
mkdir -p backups/2026
cp -a src/. dst/
mv old.txt new.txt
rm -i notes.txt # ask before deleting
du -sh * | sort -h # what is eating the disk?
ps aux | grep node # what is running?
df -h # how full is the disk?
No such file or directory names the path. Most "Linux problems" are a typo in a path or a missing permission.| grep, | sort, | tail turn a wall of output into one answer.man ls, ls --help, and tldr ls are faster than a search engine and always match the machine you are on.Every command above is a mission in the Linux track. You type it against a simulated filesystem, the server grades the result, and a mistake costs nothing. That is the difference between reading this list and owning it.
Pick one line you did not know and run it today. Tomorrow, pick another.
Keep going down the path.
A terminal that answers instantly, missions that are graded on a server, and a habit loop that survives a busy week.