Lennart Poettering unleashed systemd on the Linux world in 2010, promising to replace the creaking, inconsistent tangle of SysV init scripts with something coherent and fast. He delivered — and then kept going. systemd now manages boot, logging, networking, DNS resolution, time synchronization, containers, user sessions, and an expanding portfolio of things the old Unix philosophy said one tool should never touch. The ensuing holy war split the Linux community into camps not seen since the editor wars: those who appreciate that their laptop boots in three seconds, and those who regard systemd as a monolithic abomination that makes Lennart’s laptop boot in three seconds. Both sides are still arguing. Your server is running systemd regardless.
