The systemd Rebellion

Once a pile of 40-line bash scripts. systemd folded it all into a single switch

Until around 2010, most Linux systems described how to start each service in a shell script: dozens of lines for a single web server. This was called SysVinit. Services started one after another, so booting was slow, and restarting a crashed service meant cobbling together separate tools.

Then Lennart Poettering and Kay Sievers announced systemd, one system that starts, watches, and restarts services. But the backlash was fierce. "It violates the Unix philosophy!" critics argued. "One tool should do one thing well." The debate raged for years. Yet today, virtually every major Linux distribution (Ubuntu, Fedora, Debian, RHEL) has adopted systemd. What once took dozens of lines of startup script now fits in a few lines of configuration, a unit file.

Great tools always spark debate.