How to ditch systemd on Debian if you don't like the recent changes

https://pawb.social/post/41697756

How to ditch systemd on Debian if you don't like the recent changes - Pawb.Social

systemd recently pulled some shit, adding a field to store people’s birthdates because of a new California law. (It’s not the field itself that’s the problem, it’s how easily they’re jumping to comply with shitty laws.) This has our whole friend group rightfully freaking out. I’m pretty glad that it’s now normal to be uncomfortable with systemd, it makes me feel a whole lot less weird. I do wish the circumstances were better though. Anyway, since we switched most of our machines (all our physical ones, not our VMs/LXC containers/VPS though) to OpenRC a little while back, I figured I’d (do it again in a VM and) document the process for anyone who wants to jump ship too. Hence, my blog post! (Unfortunately if you’re on Arch it sounds like you’re a bit screwed unless you get your init system from the AUR and write all the scripts yourself. I have no idea about Fedoraland.) – Frost

I haven’t seen SystemD actually do anything. May have missed it though. What I did see is one Canonical employee make a proposal(more like an example, not one they’d actually use) on a privacy friendly SystemD check, but I haven’t heard much past that, and someone else made systemd-censord as a joke.

The way I view it though, is that we can ditch things as long as we want, but unless we absolutely clog the in boxes and call logs of state legislators showing that people won’t stand for this, nothing is going to work. And we’ll eventually be trapped anyways. And even if SystemD made an age verification service, distros could just not ship it. But Linux and *BSD distros choosing not to comply is gonna do jack shit. Telling companies like System76 to block and not sell to people in affected states isn’t financially viable and states wouldn’t care in the slightest.

If these do get passed though, and wording is made so that all software HAS to implement age verification or follow some sort of standard, what then? Sure, companies and distros could block those states if it’s just one or two. It’d be stupid and risky, but they could. But what about 5 states? 10? 30? What about all of America? What about all of the EU? What then? We shouldn’t be getting mad or stop using these products because the orgs behind them are being smart and doing minimum compliance since they have to to stay alive. We should be directing all of our attention at the people writing these laws, and try to stop them.

Do keep in mind though, that while there are plenty of people outside the Linux and general FOSS community mad about these laws, we are a small minority inside a pretty significant echo chamber. The outrage over all of this seems way louder to us than it actually is. Sad to say that, but it’s true. The vast majority of people don’t care and are fine to live in a surveillance state.

Just my two cents. I just see too many people getting mad at the groups that have no choice to comply(and are thankfully doing it in the least invasive way they possible can) instead of the actual people in charge of these laws.