11–20 of 36 posts
Anyone care to explain why SystemD is so contentious to the point it's worth forking Debian?
Whether Devuan works better than Debian with the usual systemd removal remains to be seen, of course.
Having run Debian both with and without systemd, I'm keen to try this out. Every time I hit an issue with systemd, the fix seems to involve a script anyway so experience has pushed me back to sysvinit (admittedly I'm biased in having a preference for systems simple and transparent enough I can be reasonably sure I can fix them without recourse to outside help). Whether Devuan works better than Debian with the usual s…
Isn't systemd still optional in Debian? I know there is worry that since it's the default, packages won't necessarily be well-tested without it, but afaik you can still remove it, just by installing sysvinit: http://without-systemd.org/wiki/index.php/Debian_Stretch
I had the same reaction to the initial announcement of a fork, and it's taken three years to get to an RC. (The whole systemd tempest in the tiniest, most awkward of teacups never made a lick of sense to me--in no small part because, like 99% of people, the only time I ever interact with it is when I throw a service declaration out there, and Noah Kantrowitz's fantastic `poise-service` Chef cookbook abstracts that aw…
I have been informed today that a new MySQL cluster built at work on CentOS 7.3 doesn't reliably start MySQL on boot.
We have none of these problems with our FreeBSD servers. systemd eats away at my time every week and I loathe it. It might not be a nuisance for endusers but it's a nightmare for sysadmins.
Anyone care to explain why SystemD is so contentious to the point it's worth forking Debian?
Isn't systemd still optional in Debian? I know there is worry that since it's the default, packages won't necessarily be well-tested without it, but afaik you can still remove it, just by installing sysvinit: http://without-systemd.org/wiki/index.php/Debian_Stretch
I had the same reaction to the initial announcement of a fork, and it's taken three years to get to an RC. (The whole systemd tempest in the tiniest, most awkward of teacups never made a lick of sense to me--in no small part because, like 99% of people, the only time I ever interact with it is when I throw a service declaration out there, and Noah Kantrowitz's fantastic `poise-service` Chef cookbook abstracts that aw…
At this point systemd is a whole lot more than an init system. Most people don't have a complaint with regards to systemd units or how fast it boots, it's more to do with the amount of dependencies it seems to be sucking in (at least from my experience).
Earlier quoted context omitted.
I had the same reaction to the initial announcement of a fork, and it's taken three years to get to an RC. (The whole systemd tempest in the tiniest, most awkward of teacups never made a lick of sense to me--in no small part because, like 99% of people, the only time I ever interact with it is when I throw a service declaration out there, and Noah Kantrowitz's fantastic `poise-service` Chef cookbook abstracts that aw…
As a Devuan user (not a dev), it's more than just the init system though. Devuan is also doing lots of heavy lifting to keep udev separate from systemd, as well as other things (consolekit and polkit come to mind, as does dbus). At this point systemd is a whole lot more than an init system. Most people don't have a complaint with regards to systemd units or how fast it boots, it's more to do with the amount of depend…
So they do nothing as udev and systemd already are separate packages in Debian?
Isn't systemd still optional in Debian? I know there is worry that since it's the default, packages won't necessarily be well-tested without it, but afaik you can still remove it, just by installing sysvinit: http://without-systemd.org/wiki/index.php/Debian_Stretch
so yeah, there is practically no way to escape from systemd in Debian using vanilla packages.
Does anybody really care? It took a long enough to get an RC out (3 years).
Exactly. I hope this doesn't gain traction because last thing I want as someone just writing services is dealing with sysvinit
Earlier quoted context omitted.
Exactly. I hope this doesn't gain traction because last thing I want as someone just writing services is dealing with sysvinit
You hope this doesn't gain traction because you're selfish? Devuan people aren't forcing you to write anything other than unit files. Support whatever you want and let other people freely developing their own distributions. because free software.
If GP were "selfish" he wouldn't give a rat's arse about sysvinit in the first place, but in this community you clearly don't know the first thing about, there is such a thing as compatibility-friendly development. If a config you don't like is popular, you still end up having to support it; that is why all the popular python projects I wrote are still Python 2 compatible. If I wanted to have it my way, it'd all be Py3.6 only.