Linux Sysadmin: ready for a challenge?
You understand the basics. You can find your way around, install software, look after users and keep a service running. Now it's time to sharpen those skills. In this path you stop following along and start running servers, and fixing them when they break.
Is this path for you?
You're ready if these sound familiar (each links to the lesson that teaches it):
- Moving around and managing files:
cd,ls -la,cp,mv,rm(Linux Basics, lesson 8) - Finding things with
findandgrep(Linux Basics, lesson 9) - Reading and fixing permissions:
rwx,chmod,chown(Linux Basics, lesson 10) - Installing software with
dnfon Rocky andapton Ubuntu (Linux Basics, lesson 11) - Using
sudowithout being scared of it (Linux Basics, lesson 12) - Checking and restarting services with
systemctl(Linux Basics, lesson 14)
If a few of those feel shaky, that's fine. Go back to Linux Basics for a lesson or two, then come back. Nobody is timing you.
Ready check 🎯
Five quick warm-ups using only Linux Basics skills. If they feel easy, you're ready. If one stumps you, the hint tells you which lesson to revisit.
What's ahead
| Unit | You'll learn to… | The challenge |
|---|---|---|
| Networking | read IP addresses and routes, fix DNS, use curl, nc, tcpdump and openssl | A server that can't get online. Find out why and fix it. |
| Sysadmin toolkit | logs, cron, processes, disks, backups, deploying your own app | A broken website, a hidden crypto-miner, a full disk, a brand-new disk to set up, and SELinux getting in the way |
| Shell scripting | capture output, automate with bash, write scripts that run anywhere | Turn a 20-minute chore into one command, then make it work on every family |
| Beyond Rocky & Ubuntu | AlmaLinux, Amazon Linux, Debian, and Alpine in containers | Build a tool that works out which Linux it's on, then run Alpine with podman |
How this path is different
- Things are broken on purpose. Many practice servers here start with a real problem: a site that won't start, a disk that's full, a network that's misconfigured. That's the job.
- Less hand-holding. Missions tell you what to achieve, and more and more it's up to you how.
- The sysadmin method. Read the error. Check the logs. Change one thing. Test. Repeat. You'll use it in every lesson, and for the rest of your career.
This is the part of Linux where it clicks. The first time you track down why something broke, not just how to make the error go away, you'll feel it. Take your time, break things in the practice terminal, and read every error message slowly. They're clues, not punishments.