Xenia doesn't like Systemd
Xenia doesn't like Systemd
Xenia doesn't like Systemd
Oh hey a Linux furry. Never seen that on Lemmy before
A transfem Linux furry. Completely unheard of on Lemmy.
my pearls.
I still don't know what people use to create services other than systemd
If you're writing bash scripts you're basically replicating a lot of the functionality of systemd but with larger foot guns
The system V init approach did the job fine for a couple of decades—even if the actual service definitions were a glorified shell switch statement as you insinuate.
Canonical did their upstart thing for a couple of years that wasn't too bad to use, personally I'm glad they ended up switching to systemd though.
If you're writing bash scripts you're basically replicating a lot of the functionality of systemd
You have that backwards
If you're writing Systemd profile profile profiles you're replicating shell scripts but with a lot of spongey unknown "come on, pumpkin" cancer code that you're only sure will do what you think because you don't know what suddenly capriciously changed in enterfuckingprize code and boy is your remote server screwed. Fuck me if I need to actually rely on something starting.
No one said sysV is awesome. It's built to best practice and it does what it does really well, but that's not a lot. But it does it well. Oh, the days Systemd has ruined trying to work half as well as ; well fuck, every alternative.
The days Systemd doesn't ruin, it's the other cancer, network manager and 'consistent' naming. And devices that don't come up. And devices that don't actually assign a fucking static goddamned address. #youHadOneJob
Spot the parts of enterprise Linux that runs like shit and barely does the same thing twice on two identical adjacent boxes, and I'll show you some whiz kid who shat out some cancer and went to go work at Microsoft.
So. Anyway, because the reliable stuff came before Systemd's change-for-lulz setup, you had them in the wrong order unless you have a time machine.
Maybe the arguments against systemd are issues of the past. I see people, hating systemd, bringing the same arguments of it being unstable, or constantly breaking, again and again.
However, I don't remember actually coming across any of those problems, or discussions about them, for the past 5+ years that I have been using Linux both for my computers and servers.
I have used Ubuntu, Debian, Fedora, Arch, Proxmox, NixOS. All of them use systemd.
They only problem I remember facing with systemd, which is actually never mentioned by anti-systemd people, is about its containers system, nspawn, which enables some security features by default. Those break things that tend to work with LXC without much tweaking. Docker, for example, may face issues running inside nspawn.
Very much this, why is systemd entangling itself in every part of the linux kernel, I ripped that mfer network-manager and installed iwd
I'm on guix-sd and don't have to suffer systemd
Amen.
the fuck is this?
"Systemd controversy"
I think the controversy ended 10 years ago. It is crazy this is still something people will bring up from time to time.
Unlike Extended Memory.
I still say you EM users are playing with fire.
I don't get all the hate for systemd. Chop Suey is an absolute banger.
ngl I quite enjoy using systemd
I hace a Xenia sticker on a machine that enthusiastically runs SysD.
Well you shouldn't. Take it off immediately, systemd or the sticker, either will do. She's stated her position on the matter, and you should respect that!
(/jk I'm not actually having a go at you, stickers are cool, and systemd is pervasive)
Was gonna ask what's wrong with Systemd but decided to look it up and I now see why, at least from what I was reading.
I mean, if you want an init (e.g. embedded linux), sysd may not be way you want. On desktops, tho, you ultimately end up hacking together more or less the same functionality with sticks'n'shit. And yes, sysd timers are more readable than crontab, sue me.
Edit: the point is, sysd is not (only) an init.
It's fine, people will whine about anything.
Ah, thanks for the reminder! As a happy systemd user I sometimes forget how stubbornly resentful some people in the Linux community are that they still try to keep this up as a topic. Then again, maybe this is just a troll?
cringe
Yeah, more like "cringe deez nuts."
fair point
furry
hates systemd
thinks anyone still uses PulseAudio
Three wrong opinions in such a short post, impressive.
calling furries wrong opinions in a Linux community
That's a bold move Cotton let's see if it pays off
I am typing this from a device which uses PulseAudio (FuriLabs FLX1 phone). I wish it used pipewire instead, but for now I don't really have a choice. Pipewire doesn't work yet with everything on this phone, so everyone with this phone is using PulseAudio (unless they don't want working audio).
How is furry an opinion?
And how can an opinion be wrong?
You can not say someone is wrong hating someone/something, if they do it, it is a fact and if not, it is a lie. And you have no way proving that.
And lastly, thinking that most people use PulseAudio is a supposed fact, which can be true or false, but is not an opinion neither.
But you can definitely say that your opinion is that furry as a culture is wrong, that hating systemd is wrong and that thinking anyone still uses PulseAudio is wrong.
I must add, you have strange opinions…
Well, opinions can be wrong. When someone says an opinion is wrong they don't mean that it's not true that you have that opinion, but rather that it's an opinion you should not have.
And some opinions like any other ideas are just wrong. You are entitled to have them, just as much as you are entitled to be wrong, it doesn't change the fact that it's wrong.
For example "we should change math so that 25+75=100" is an example of a wrong opinion.
Systemd is great
I love Podman Quadlets
Average
journalctl
avoider