4 ms·
I really don’t get this mentality. Where are you limited exactly? You can trivially view and edit every single service file to achieve basically anything. But a
by kaba0 6y ago
I really don’t get this mentality. Where are you limited exactly? You can trivially view and edit every single service file to achieve basically anything. But a modern system does require some building blocks. I mean, the linux kernel is similarly limiting you to eg. have a file-oriented abstraction, and you can’t just swap it out to a different kernel. Systemd is much more modular than that for example.
- lmm 6y agoPre-systemd you actually could switch out the kernel on Debian - you could be running Hurd or the FreeBSD kernel, but the rest of the OS would still be Debian.
- kaba0 6y agoI believe it is only correlation, not causation. I think it has more to do with the linux kernel being much more advanced than the others, and some of the userspace depending more and more on these advanced features. But I’m not sure about this. Aren’t you referring instead to debian itself providing packages for all of them and the package manager running on each distro? Because I can’t really believe you could just swap out the kernel and be on your way in most cases. If it is the latter, than it was more due to the fact that debian maintainers voted against supporting other systems, because it is a great amount of additional work.
- lmm 6y ago> I believe it is only correlation, not causation. It's a bit more direct than that - previous init systems were kernel-agnostic whereas systemd is explicitly tightly coupled to Linux and udev, and encourages the rest of userland to be tightly coupled to it. > I think it has more to do with the linux kernel being much more advanced than the others, and some of the userspace depending more and more on these advanced features. I wouldn't say "more advanced" - in many ways FreeBSD jails are a better technical solution than Linux's various container systems.
- zepearl 6y agoI think that lmilcin was referring to "either use systemd on distribution X or switch to another distribution". E.g. in Gentoo you can choose to use SystemD or OpenRC, but I think that most other distros don't provide such a choice.
- kaba0 6y agoMost don’t provide such a choice, because it’s a huge undertaking to basically package and maintain 2+ versions of everything, especially when one is unified among distros and often created upstream. And of course after a certain size it has to do with network effects, but it was chosen based on merits — for example debian voted multiple times on the issue and I would say their voting system puts most countries’ to shame. I believe up until recently the vote on debian was basically use systemd but if the maintainer wants to, they can also support alternative init systems, but there was not much interest. But of course anyone can help the fringe distros on another init systems to make them less fringe.
- zepearl 6y ago> Most don’t provide such a choice, because it’s a huge undertaking to basically package and maintain 2+ versions of everything Yes, I absolutely agree regarding the effort. (not sure about that vote - I honestly didn't follow that discussion) In parallel, some software (cannot recall - maybe the Gnome window mgr) does rely (in its original form) on SystemD being there => I don't think that's fair, kind of forcing the distros that want to offer it to adopt it => I don't like it - I do see the advantage of having that kind of integration, but I still don't like it :P
- spiralx 6y agoGnome's dependency on logind came about because there originally was a dependency on a different library that one person had written, had pretty much stopped working on, and nobody wanted to take on maintaining it or adding it to Gnome itself. The dependency no longer exists because some people took logind from systemd, made it a standalone package and called it elogind lol, and now you can use that instead of logind.