cross-posted from: https://lemmy.ca/post/62192988
The latest changes implemented in the Systemd repo, related to or prompted by age-verification laws, have made many people unhappy (I suppose links about this aren’t necessary). This has led to a surge in Systemd forks during the last days (“surge” because there have always been plenty of forks). Here are some forks that explicitly mention those changes as their reason for forking (rough time ordering taken from the fork page):
paramazo/systemd “The systemd System and Service Manager without age verification”
ganitam/systemd “Systemd fork just before the Age Verification addition. Hoping more capable developers and maintainers do same…”
GSYT-Productions/systemd-fork “The systemd System and Service Manager, without the stupid Age Verification”
speedythesnail/unre tarded-systemd “The systemd System and Service Manager, without the r e t arded age-verification commits”
ta13579/systemd “The systemd System and Service Manager WITHOUT THE FUCKING AGE CHECKS”
r4shsec/systemd-no-age-verification “This is systemd but without the age verification made via pull request https://github.com/systemd/systemd/pull/40978”
Pingasmaster/fightthesystemd “Systemd without the nonsense: no age verification, no lighthouse built-in.”
Jeffrey-Sardina/system “Liberated systemd – no surveillance. Ever.”
HaplessIdiot/systemd-saneagecheck “The systemd System and Service Manager with age verification bypass and polling rate options for said feature”
Queer-Coded-LGBTQ/systemd-fuck-california “The systemd System and Service Manager, but without age bs added in.”
Codiak540/unshitted-systemd “A fork of systemd aiming to strip the Age verification. Sue me california.”
Hopefully the energy of this reaction won’t be scattered among too many alternatives, although some amount of scattering is always good.
It’s concerning how dismissive people are about this change considering this is the first in a long line of adversarial changes to what is a critical piece of software.
It is. My impression, which can be completely wrong, is that it’s mostly younger generations, who have not experienced this kind of danger and inch-wise progression, and therefore underestimate it.
I’d rather just go back to sysvinit tbh.
openrc’s pretty great too. Nice to write scripts for (…but writing sysvinit scripts gives you compatibility with other init systems for free, so…) and has user services and stuff.
Never tried any of the other other init systems, but there’s plenty out there!
100%
Why trade one metastatic syphilis for another? Just go back to what worked and gave us reliable, fast boots, no fstab fuckery, and no “I’m sorry I can’t shut down because I was designed by a guy who wanted to work at Microsoft (and now does)” bullshit. It’s all fucking baling wire.
Heaven forbid we need to learn what xinetd is for, or how to make a fucking loop in a bash start script.
The stop job bullshit pisses me off so much. I shut down the computer because I want it off JUST KILL THE PROCESS.
This drives me absolutely nuts. For my Linux machines, I just type
sudo shutdown nowand that does the trick no problem. 9 times out of 10 I have a terminal window open anyway.But my work laptop running Windows 11? lmao, after deliberately shutting it down on Friday last week, I just pulled it out and opened it up to a prompt from Outlook saying “Do you want to delete everything in ‘Deleted items’?” and a nearly-dead battery. Thanks Microsoft. That’s definitely what I want it to do when I hit “SHUT DOWN”.
Agreed. I prefer windows to shut down as God intended: without any notice while I’m playing a video game so that it can do some stupid update.
I wouldn’t personally. But either way all these forks are silly considering the non issue they’re addressing. Though it’s their developers, God-given time to waste. Should they choose to.
It was a merge request from an external unassociated developer. To add an optional text field to a bunch of other already optional and generally unfilled text fields. With no method to check or enforce anything. To the nameD subsystem of systemD. If the text field offends you don’t fill it. Save your powder for those implementing checking and enforcement.
I can definitely see both sides. On one hand I do agree the actual change itself is pretty meaningless. Just don’t fill the systemdb entries with any info. However what the change represents is much more alarming. It signals a foot in the door to open source devs conplying to the authoritarian whims of a governmental power. They should definitely not comply with dumb legeslature like this, especially considering their userbase.
TLDR: the change itself is dumb and small, but what it means for the foss community is much more alarming and dangerous.
I still don’t. Unfortunately these groups are still required to follow laws regardless of how stupid they are. And many more than this are indeed, very stupid.
If you want to have riteous anger at someone who deserves it that might have positive impact. Rail against the governments. Not to downplay what happened in Nazi Germany. But would you think it reasonable to harras and harangue German Jews who wore the star of David to identify themselves as required by the government? I don’t think a reasonable person would. When I bump into groups that have to comply with stupid state laws here where I live, I don’t blame those groups. I blame the state like any sensible person would. Not attacking and blaming other victims of the state.
Do you think they should resist the state? That’s all well and good. Will you be there to defend them when the state comes? To fund these random devs defense? No? You won’t and they’re largely on their own? Then what do they owe to us? What entitles us to give them so much grief?
The pr was merged. It’s not just a request from an external developer any more, it’s part of systemd.
Yep, and uncontroversial in and of itself.
uncontroversial
Evidently not, as shown by all the forks.
You’re confusing blind reactionary panic with controversy. But hey, it’s your chance to prove me wrong. Tell me what the controversial change was. And why a completely optional text field with no check or enforcement or any system behind it is controversial. Do you even know anything about the subsystem being discussed? Because if you did all the outrage is absurd.
I would say that if it causes a controversy then it is controversial, even if some people think it shouldn’t be.
Oh, I got you now. You’re one of those people that thinks vaccines are controversial. Because a bunch of uninformed or misinformed people have bad opinions on the subject. And if you’re not. That’s worse because you can’t be bothered to have any consistency lol.
There’s a difference between a controversy or conspiracy, existing around something. And that thing being controversial itself. And I’m going to get a lot of downvotes for pointing that out. But I’m not even mad. It’s absolutely true and hilarious to watch all the uninformed reactionary downvoting.
BTW dawg. Got bad news. All Unix’s have been similarly doxing us likely longer than you’ve been alive!!! With completely optional, unenforced, and voluntary fields for such sensitive information as real-name address and even date of birth. Dun dun dun!!! Not even that recent unearthed tape of bell labs sysIV was clean! Unix is a voluntary CIA psyop confirmed! Welp better go harass volunteer projects and devs who are also victims of these failing states. That will fix it if anything will. Because if there’s one thing we all know for a fact. Ignorant reactionary mobs are never wrong.
Almost sounds like a grave overreaction to nothing.
Agreed.
