On the Tragedy of systemd
Spent a decent portion of my professional life with init.d. Had to deploy a set of Ubuntu servers last week (use FreeBSD at home), which marked my first actual brush with systemd after a long while of sysadmin-ing Linux systems. It’s weird, takes some getting used to, and has a lovely Enterprise™ smell to it1, but I don’t think I mind it too much, especially with a nice cheatsheet. Just ergonomics; no comments on its security and stewardship 🤐
I wanted to know more about it’s history and enjoyed this really excellent talk by Benno Rice. Had no idea that its creator received death threats and various other forms of online abuse over an innocuous set of ideas and piece of software. Unbelievable.
Some select quotes from the talk and about systemd:
People have a complicated relationship with change. I like to say that nerds especially have a really complicated relationship with change. We love it to pieces. Change is awesome when we’re the ones doing it.
The moral isn’t “Don’t use systemd”, the moral is “Write stuff in better languages than C”. rsyslog doesn’t exactly have an enviable security record either.
and finally,
The moral is “Don’t use systemd. And don’t chain core system functionality to software from teams with a track record of imcompetence.” It’s about better, experienced programmers. Not “better” languages.
Word.
-
I imagine that
init.ddid too when it was introduced. ↩︎