systemd

systemd is the init system and system manager that became Linux's default boot answer — announced by Lennart Poettering and Kay Sievers in April 2010 with the essay "Rethinking PID 1", and first shipped as a distro default in Fedora 15 (May 2011). It replaced SysV init's ordered shell scripts with a dependency graph of units: services, sockets, timers, mounts, and targets that boot in parallel because the graph — not a numbered list — decides ordering.^[1]

What it actually is

The name covers more than PID 1: systemd is a family — journald (binary structured logging), systemd-boot (the EFI bootloader formerly gummiboot), networkd, resolved, timesyncd, logind, homed, plus systemctl/journalctl/hostnamectl as the control surface. It absorbed udev in 2012. Its defining mechanics: socket activation (services start when their socket is touched), cgroups-based process tracking (no daemon can escape its service), and declarative unit files instead of executable scripts.^[2]

The controversy — stated plainly

systemd's takeover was Linux's loudest civil war: critics argued it violated Unix's do-one-thing philosophy and became an unportable dependency web; defenders pointed at parallel boot, reliable process supervision, and the death of PID-file guessing. Debian's technical committee voted for it in February 2014 — the dissent produced Devuan, and Gentoo, Slackware, Alpine, and the holdout families still boot OpenRC, SysV, or runit. Whether you run it or refuse it, chapter 17's boot anatomy is systemd-shaped on the majority of modern installs.^[3]

See also

• Inside a Linux System — the boot chain it sits in
• Logs Monitoring and Time — journald's side of the story
• Processes — cgroups and service supervision
• Linux · GRUB · Glibc