systemd Training
Services, cgroups, the journal, boot — practiced, not skimmed.
Coming soon
You work through 27 sections on a disposable Linux VM. Each one opens with a short refresher, then hands you a lab: write the unit, break socket activation on purpose, watch what the journal records while you do it. A knowledge check closes every section — 386 questions across the course, and you can retake them until they stick.
Status: all 27 sections are written and in final review. Enrollment opens soon.
Self-paced and text-first. You read, you type, you check — no video timeline to scrub.
From unit files to image-based updates.
Every section pairs a concept refresher with a hands-on lab and a knowledge check — 386 questions across the course. Open a part to see its sections.
Environment check, conventions, and how the course works
Part I Foundations 4 sections
- 1 Why systemd
- 2 Inside the Managers
- 3 Unit Files
- 4 Dependencies and Transactions
Part II Service Lifecycle and Activation 6 sections
- 5 Service Types and Readiness
- 6 Execution Context
- 7 Failure and Recovery
- 8 Socket Activation
- 9 Timers, Paths, Devices, and Automounts
- 10 Transient Units and Control APIs
Part III Resources, Isolation, and Identity 4 sections
- 11 Cgroups, Slices, and Scopes
- 12 Service Sandboxing and Hardening
- 13 Credentials and Secrets
- 14 User Managers, Sessions, and Identity
Part IV Observability and Reliability 4 sections
- 15 The Journal
- 16 Diagnosing Units and Boot
- 17 Failure Evidence and Memory Pressure
- 18 A Production Service
Part V Boot, Devices, and Storage 4 sections
- 19 Boot and Shutdown
- 20 udev and Device Management
- 21 Mounts and Storage Assembly
- 22 systemd-boot, UKIs, Secure Boot, and TPM2
Part VI Networked and Image-Based Systems 4 sections
- 23 systemd-networkd
- 24 Name Resolution, Time, and Host Configuration
- 25 Containers, VMs, and Extension Images
- 26 Image Lifecycle and Atomic Updates
Read a little. Break it in a lab. Prove it stuck.
The same rhythm in every section, so the course gets out of your way and the material does the work.
Read a little
Each section opens with a compact refresher in the browser — a few minutes of reading that sets up exactly what the lab needs, and nothing more.
Break it in a lab
Numbered steps with checkpoints, run in your own terminal. Solutions stay one click away, not in your face. For systemd, that means nothing more than a throwaway Linux VM.
Prove it stuck
A knowledge check closes every section: 70% to pass, unlimited attempts, and the multi-select questions are all-or-nothing — exactly correct or try again.
self-paced · text-first · runs in your browser and your terminal
For people who work in a terminal already.
No graded deadlines and no cohort schedule. The course assumes you are busy, curious, and allergic to filler.
- Linux administrators and SREs who operate systemd services every day and want to predict the manager rather than poke it.
- Teams adopting sandboxing, cgroup resource control, and credentials, who would rather break these things in a lab first.
- Anyone fluent in
systemctl restartwho wants the model behind it.
Coming soon.
This list exists to tell you when systemd Training opens for enrollment. Expect a launch note, not a newsletter.
The signup uses double opt-in. Every message includes an unsubscribe link.