are some of the supposed systemd alternatives run by fascists? yes they are. a do-everything init ecosystem is an irresistible lever of power for them. init should be thin and independent enough that it isn’t an ecosystem at all, but if we must have an init ecosystem then we must be very careful who controls that power. again, ideally, there should be no power to control.
with that said, can we please stop fashjacketing all of the people who recognize systemd and wayland as levers of power?
systemd isn’t how most software is shaped. we don’t need to recreate this particular set of mistakes to have a modern init.
“but @zzt what alternatives can you recomm—“ openrc. openrc on alpine or gentoo. openrc is thin enough and reputationally made by people who don’t fucking suck. it’s well-designed. you probably won’t hate it, and the only bits of systemd you’ll miss are the bits there to lock you in.
there’s plenty of other alternatives. don’t post the fash ones or I’ll get fucking mad.
@hipsterelectron @zzt Anxiously looking for an exit I came across this
> WARNING the instructions are intuitive rather than comprehensive.
@zzt
There's even Shepherd.
(The Guix team have been quite noticeably pulling away from the FSF for a while now)
@lizzy the best examples I have of the ones reaching for an ecosystem are fortunately dead systemd forks run by absolute assholes.
the ones I’ve seen pointed to as examples in modern discourse are suckless init, which I don’t think anyone uses (for good reason, it’s baby’s first init made by nazis), and devuan, which doesn’t actually run an init project of its own but which is the most visible fascist anti-systemd ecosystem.
@jwz that’s fine, they’re both trash
keep an eye on your timeline for posts from within the last 12 hours or so lamenting how much of the critical Linux userland infrastructure under systemd just became slop for a worked answer to your question. we’re unfortunately past the point where the damage is theoretical.
@zzt honestly it doesn't even feel like a gotcha or "i told you so" moment, people got tricked into abandoning redundancy for their systems, and now are left to pick up the pieces with the guilt that they helped push something that ultimately ended in a disaster.
it's all just sad
@uproot4269 @zzt i'll be extremely honest, the chance of a succesful systemd fork is close to 0. project forks only work when you have people who already at least somewhat know how the project works, preferably existing recurrant contributors (because if you did one contribution 5 years ago that fixes a typo somewhere, you don't know anything about the project's concrete structure) and maintainers, but if the maintainers themselves are pushing for things harming everyone else, they're not going to be on board.
also, the very architecture and design of systemd, aka, taking every component and putting them, tightly coupled, into a single mostly homogenic slab of code is exactly the reason why we got into this mess, a fork will not fix that