2 ms·
Systemd's a lot more than an init system, and that's no accident. Red Hat now determines where Linux goes in some very important ways, and I think they believe
by bamfly 3y ago
Systemd's a lot more than an init system, and that's no accident. Red Hat now determines where Linux goes in some very important ways, and I think they believe they've finally got a solid lock on that, after years of effort, if they're making this move. Why go with a competitor (if you're a paying customer, which is who matters) that's just following in Red Hat's wake? And now, the options for RHEL-in-a-different-label will be gone. Who's left? Nobody, you're gonna pay Red Hat or eat extra (perceived, if not actual) risk.
[EDIT] Nb that for the above it doesn't even matter if Systemd's better than the pile of interchangeable daemons and programs it replaced. I have opinions on that, but it's irrelevant to Red Hat's market maneuvers, aside from that it was important to them that it not be easy & safe to cleanly replace, in part or whole.
- sho_hn 3y agoHave you looked at 2022/23 commit logs for systemd and matched those authors to employers? (Preview: It's mostly Microsoft, Meta and Suse.)
- progmetaldev 3y agoI think that's why this current issue is more relevant than ever. Red Hat is burning goodwill they had, which is going to eventually start to cut into the types of decisions they used to be able to make when they had more community "power". I've always enjoyed using Debian (or Debian-based) systems than Red Hat (or Red Hat-based) systems, and was unhappy when I had to re-learn init scripts, but at this point in time Systemd just seems to be easier with some features being "free" to restart or figure out systems that don't restart automatically.