Originally posted by Shiba
View Post
Fast boot times, while universally attractive, wasn't the main selling point of systemd; it was getting rid of hard to parse and maintain shell scripts and replacing them with plain text config files, and having an init-system with the logic to handle complex dependencies instead of leaving it to humans to hand graft those.
systemd also provided the first real service management system that Linux ever had, and now provides a defence-in-depth security framework that leaves non-systemd distros in the dust.
In short, systemd won out because of overwhelming technical superiority, not good advertising of a single feature.
Originally posted by Shiba
View Post
You clearly aren't well informed about the technical functionality of systemd. Of course systemd works with CK or CK2 or whatever instead of systemd-logind. The core of systemd; systemd (the deamon), udev and journald is rather tiny, and everything else is optional. You can use whatever you like.
That you can't rip out random pieces of systemd an expect them to work on non-systemd distros isn't a useful criticism. In case of systemd-logind the basic fact that OpenRC etc. don't use Cgroups to name and track processes makes it impossible to use. It is like demanding that some random tablefunction in Libreoffice should magically work on Vim or ed.
Claiming that systemd "absorbs code" makes you sound that you never heard of Open Source code before. LGPL code can't be "absorbed" in any meaningful way. Udev was invented and maintained by systemd-developers, and they made it easy for non-systemd distros to fork, hence "eudev". Care to name any other projects that got "absorbed" into systemd?
Originally posted by Shiba
View Post
Leave a comment: