31 ms·
"Having [systemd] installed but inactive makes MX compatible with the increasing number of apps which require this shoggoth of a startup daemon, but thanks to a
by mikece 3y ago
"Having [systemd] installed but inactive makes MX compatible with the increasing number of apps which require this shoggoth of a startup daemon, but thanks to a package called systemd-shim it's effectively disabled unless you specifically choose it from the boot menu."
Is systemd really a relevant reason to argue in the Linux community? I find it amusing that the anti-systemd folks cite the UNIX philosophy as why they don't like systemd... uh, this isn't UNIX, it's Linux!
- Bender 3y agoFor me personally Linux and UNIX are about having many options and a million ways to accomplish a thing so I think it's great that there are distributions free of systemd. I used systemd for a while and while I was not happy about it being implemented without alternatives I tried to make the best of it. I liked the idea. I liked some of the capabilities, though runit and supervisord could have been improved to accommodate those capabilities. It became even more bloated and took over too many functions for me and started making decisions that I felt were not appropriate for an init replacement so I personally just opted out of it. The integration with udev and binfmt started to appear as the same obfuscation and vulnerable designs that early versions of Windows and MacOS had. Rather than engineering the same mitigations that Windows and Mac required I decided it was time for systemd and I to part ways. Others can take on the tasks of re-implementing the lessons learned whereas I just want a computer that does as it is told with mostly predictable results and very minimal obfuscation so I can troubleshoot problems easier. I believe this comment will make more sense as time passes.