Linux System Administration: From Terminal to Production
About this course
What this program is really about
Most people who start working with Linux servers learn just enough to get through their current task, then panic the next time something breaks. This program is built around a different idea: you should understand what the system is doing, not just how to make it stop complaining.
We cover the full operational layer of a Linux system — processes, services, users, storage, networking, and logs — with a strong focus on reading what the system is telling you and responding to it sensibly.
Who tends to do well here
People who already touch the command line occasionally but feel like they are operating on guesswork. Developers who manage their own VPS or staging environments. Junior system administrators who were thrown into production without much onboarding.
You do not need to be a programmer. You do need to be comfortable opening a terminal and willing to break things in a safe environment.
A few specific things you will work through
- Service management with systemd
- Writing unit files, handling dependencies, reading journal output when something refuses to start.
- User and permission management
- Understanding how Linux file permissions actually work, including setuid bits and ACLs that most tutorials skip.
- Storage and filesystem basics
- Partitioning, mounting, checking disk health, understanding what happens when a filesystem fills up at 3am.
- Network configuration and diagnostics
- Static IPs, routing tables, firewall rules with nftables, diagnosing connectivity issues with real tools.
- Log analysis and monitoring basics
- Using journalctl, grep, and awk to find the actual cause of a problem instead of rebooting and hoping.
How the sessions run
Each session includes a short explanation followed by a practical task in a lab environment. You get a real virtual machine, not a simulated terminal. If you misconfigure something badly enough to break it, there is a reset button — but we encourage you to troubleshoot first.
There are eight live sessions across four weeks, each about ninety minutes. Between sessions, there are short assignments meant to take thirty to forty minutes, not hours.
What the workload looks like
Honest estimate: about five to seven hours per week if you want to absorb the material rather than just complete the tasks. Some weeks are lighter, particularly the first two while we are covering fundamentals.
What about Windows-based systems?
This program covers Linux only. There is a separate program focused on Windows Server environments if that is your context.
Learning program
Program structure
- Week 1 — The system underneath
- Filesystem hierarchy and navigation without getting lost
- Process model: what actually runs and how to see it
- Users, groups, and the root account in real environments
- Week 2 — Managing services and software
- systemd in depth: units, targets, dependencies
- Package management across Debian and RHEL families
- Scheduling tasks with cron and systemd timers
- Week 3 — Storage, networking, and security basics
- Disk partitioning, LVM, mounting filesystems
- Network interfaces, routes, and firewall configuration
- SSH hardening and basic access control
- Week 4 — Monitoring, logs, and incident response
- Reading and filtering logs with system tools
- Setting up basic alerting and health checks
- Working through a simulated outage scenario
Each week ends with a short written reflection: what broke, what you learned, what you would do differently next time.