Systemd, from /dev/null to root
summary
An introduction to why systemd replaced SysV init in modern Linux distributions and how its unit files (stored under /lib/systemd with overrides in /etc/systemd) let the OS manage service lifecycle instead of shell scripts. Covers concrete tools and paths — systemctl, systemd-analyze, systemd-run, systemd-verify, journalctl — and features like socket activation on demand, dependency declarations (Requires/After), centralized logging via the journal, and resource limiting with slices and cgroups.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:35Speaker background
- 7:50Why systemd replaces SysV
- 10:14Service units in systemd
- 15:07Basic service commands
- 19:20Developer benefits
- 23:11Advanced units and features
- 28:52Ecosystem and tools
- 34:13Conclusion
related talks
27mSystemd: why you should care as a Python developer
22mWhat's new in systemd in 2016?
38mWe Need to Talk About Systemd: Boot Time Optimization for the New init daemon
54mSystemd-Nspawn is Chroot on Steroids
23mReboot Without Rebooting: Updating Linux Userspace at the Speed of a Service Restart
18mUsing Systemd to Ship Container Runtimes. How?
37mAccelerating Linux Boot Time: Techniques and Strategies for Optimal Performance
48mThe Unix Way Seen by a DevOps