Ok. Here’s the thing. I don’t know how linux works. I don’t know what systemd is. All I know is that all around the world we got clowns who know less about linux than I do trying to dictate the entire worldwide internet to cater to their specific geographical location, regardless of where the user is.
Then I hear systemd is openly trying to bow at the knee before these laws are even in effect.
And yes, the current system is you as a user inputting your birthday with zero verification.
But the gov of california has already said that before these laws go into effect they’ll be looking for stricter laws with checks in place. These systems are not in place now. Nor do they even know what they will turn out to be.
When asked about this, the gov said “We’re working on it.”
Then systemd comes along, ready to bend all of linux to their whims. So I put two and two together and decided this whole thing is pissing me off.
Pervasive, yes. Deeply embedded in the distros that uses it, absolutely. And I get why people don’t like binary logs, although that isn’t exactly relevant to monolithic vs pluggable.
You seem to think that I’m arguing against your opinion that systemd is bad. I’m not. I’m arguing against the false statement that it is monolithic. It isn’t. It’s modular, like the linux kernel. If you wanted to remove every component except the init system, you could. Big pain in the ass to do that, but you could.
Absolutely. That’s not what happened though. It’s a birthdate field with no verification. The point is to show how stupid the laws are.
Don’t hate systemd for age verification
Hate systemd for its monolithic, anti-Unix design pattern
Ok. Here’s the thing. I don’t know how linux works. I don’t know what systemd is. All I know is that all around the world we got clowns who know less about linux than I do trying to dictate the entire worldwide internet to cater to their specific geographical location, regardless of where the user is.
Then I hear systemd is openly trying to bow at the knee before these laws are even in effect.
And yes, the current system is you as a user inputting your birthday with zero verification.
But the gov of california has already said that before these laws go into effect they’ll be looking for stricter laws with checks in place. These systems are not in place now. Nor do they even know what they will turn out to be.
When asked about this, the gov said “We’re working on it.”
Then systemd comes along, ready to bend all of linux to their whims. So I put two and two together and decided this whole thing is pissing me off.
Systemd isn’t monolithic, it’s a pluggable framework with a shit load of components
ok so tell me why I’m waiting for networking to come up before I’m allowed to interact with my computer
Also, its monolithic as heck, its a giant squid into my networking, time management, access control…
Ontop of that… binary logs ew.
Because your distro sets up stuff weirdly? At least I never noticed networkd to be a dependency of multi-user.target, could be wrong though.
That’s all optional though, many distros just use it because it’s easier than the alternatives.
Yeah, that’s indeed stupid. No clue why they did that.
Pervasive, yes. Deeply embedded in the distros that uses it, absolutely. And I get why people don’t like binary logs, although that isn’t exactly relevant to monolithic vs pluggable.
You seem to think that I’m arguing against your opinion that systemd is bad. I’m not. I’m arguing against the false statement that it is monolithic. It isn’t. It’s modular, like the linux kernel. If you wanted to remove every component except the init system, you could. Big pain in the ass to do that, but you could.
It replicates a lot of unix tooling poorly, bound to the Systemd framework which runs only on Linux. So, still a monolith.
That’s … not what monolithic means, in software architecture