5 ms·
> In short: merging elogind appears to be complex enough that it would be hard to justify in the absence of a strong commitment to the support of non-systemd in
by flukus 7y ago
> In short: merging elogind appears to be complex enough that it would be hard to justify in the absence of a strong commitment to the support of non-systemd init systems.
I think that outlines the problem well, systemd might be a good init system but it's not just an init system and it's an all or nothing thing. There is no meritocracy of components which has always been a strength of linux.
- ghostpepper 7y agoIs systemd designed in a modular way that makes it easy to use systemd as the init system without importing the kitchen sink?
- parrellel 7y agosystemd is sadly a horrible cancer blob of dependencies. edit: as of a couple of years ago when I last had the time to care. I suppose it's possible something has changed, but I doubt it.
- ac29 7y agoSure - for example, systemd can synchronize your system time with NTP, configure your wireless network, and run periodic tasks if you'd like it to. Or, you can use different tools to do those tasks and everything works just fine.
- freedomben 7y agoSome things are, others aren't. For example systemd-resolved is highly optional. Some distros include it, others don't.
- flukus 7y agoNo, hence this article. Note that the system they're having such a hard time integrating is a fork of a systemd component, which is about as close to the best scenario as you could hope for.