The Motte is all the shovelware attached to systemd that is nearly impossible to detatch and the Bailey is the init replacement.
Linux distros without systemd
31–40 of 449 posts
Re: Linux distros without systemd
#32Love this! Notice that the text about slackware sounds a bit "pessimistic", as if it was a somewhat legacy distribution. Nothing further from the truth. We run a small farm of virtual machines with different up-to-date distributions, and slackware is typically the one that follows upstream packages more closely. For example it had gcc 9.1, bash 5, etc. a few days after they were released.
Re: Linux distros without systemd
#33Earlier quoted context omitted.
The objections to systemd are still as valid as ever. We still see a pretty high rate of security vulnerabilities in it. However, as projects adopt systemd-proprietary APIs, distros are forced to choose between maintaining ongoing forks of those projects, dropping those projects, or adopting systemd. E.g. I suspect Slackware only avoided being forced to adopt it because they'd already decided to not support gnome.
High rate? Compared to the Linux kernel, systemd's CVE rate is very low.
Re: Linux distros without systemd
#34Earlier quoted context omitted.
High rate? Compared to the Linux kernel, systemd's CVE rate is very low.
Do you have a source for it?
https://www.cvedetails.com/product/47/Linux-Linux-Kernel.htm...
https://www.cvedetails.com/product/38088/Freedesktop-Systemd...
For a piece of software used by millions of machines, that's a very low CVE count.
Re: Linux distros without systemd
#35I get no end of bemusement from open source advocates that think it makes any kind of rational sense to campaign against an open source project. THIS IS ALL OPEN SOURCE. Freedom and choice is the whole point, isn't it? If you prefer an alternative or forebear to systemd, that is great. Use it. Advocate for the system you prefer. Convince people that the choice you have made is better. Meanwhile the vast majority of d…
It's worth realising that the GNU project could never have happened in the first place - Linux could never have been a thing - if historical Unix had been designed like systemd.
Re: Linux distros without systemd
#36I get no end of bemusement from open source advocates that think it makes any kind of rational sense to campaign against an open source project. THIS IS ALL OPEN SOURCE. Freedom and choice is the whole point, isn't it? If you prefer an alternative or forebear to systemd, that is great. Use it. Advocate for the system you prefer. Convince people that the choice you have made is better. Meanwhile the vast majority of d…
Notice that nobody complains about the existence of systemd, but about the enormous and shady pressures that distros had (particulary debian) to adopt it as standard. Nowadays, the complain is mostly about the systemd monoculture.
Re: Linux distros without systemd
#37I get that not everybody likes systemd, but a lot of the criticisms seem misguided and looking at sysvinit with role-colored glasses. For example, people are complaining about logind being included, but forget that consolekit was unmaintained before that. Yes, there's parts to systemd that not everyone will use, like container support, but in that case you can pretty safely ignore that use case. For me, systemd has p…
I don’t think anyone thinks that sysvinit is better than systemd, but RC definitely is.
Re: Linux distros without systemd
#38SystemD definitely spurred some controversies years ago but is it that bad in 2019? All major distros adopted it and even some that are listed there as "no systemd" in reality just give you choice (e.g. Gentoo). I'd gladly hear the opinion of distro maintainers why did they switch to SystemD if it's as bad as it looks like in people's perception.
every few days I discover some new bit of non-determinism:
- systems getting stuck for long periods at startup or reboot with with some useless text like "Waiting for user session to shutdown"
- reboots never completing at all (getting completely wedged shutting down)
- jobs starting in weird orders, like crond starting up before the network, causing various things to break in new novel ways (sometimes, not always)
I can fix most of these systemd-created issues one by one as I discover them, but it's hardly making my life easierRe: Linux distros without systemd
#39Re: Linux distros without systemd
#40Personally, while I do think that systemd's scope might have been a bit too ambitious, I do find it easier than something like Upstart