Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
In reference to: https://lemmy.world/post/23862757
I use Void btw
Image text:
Most people rejected his message.
"Systemd is Satan's creation! Pure Evil!"
They hated Talking Pig because He told them the truth.
Just the meme/thread I was looking for. As someone that's been out of the linux game for awhile, what's the lastest on the controversy here? Do the systemd haters look more or less correct in the year 2025?
π€Hail Systemd!π€
system d struggle sessions should be integrated into SystemD
Install what you want we're in the land of the free (and open source software) here
Hueheue i use artix btw
redpill me on artix. Why should I switch from something like gentoo that still enables me to avoid systemd?
I tried gentoo a while ago and couldn't figure out portage, but that's on me... The reason i switched to from standard arch was just because my pc took 3 miniutes to boot (from nvme) and changing my init sys to runit solved my issue. I'd love to actually figure out gentoo someday though
There's a support channel on irc for things like this. Also portage is just a better pacman--it can do more and thusly a time investment is necessary to be in control of your hardware
I still can't wrap my head around why SystemD has become the defacto standard & why aren't devs trying out OTHER init-systems
Imagine trying to get new, young developers to adopt C or Pascal when the likes of Rust and Python exist. You can make arguments for a thing's superiority based on moral standards (which are always subjective), but morality is a poor metric. If everything was done based on that, the Linux ecosystem would be in the same state as the GNU Hurd kernel.
The choice of init system is up to the distro maintainers because init scripts are usually created and maintained by the packager of a given application. Debian for example chose its init system via a democratic vote. Distros that focus on different init systems exist, like the Debian fork Devuan.
It's pretty good at starting services. It just keeps adding bundled things people wouldn't use otherwise, in a fairly microsoft fashion
Is systemD open source ?
There's also no uppercase d in systemd, the word is entirely lowercase (but I'll still write it with an uppercase s at the start of sentences).
been out of lemmy for a while, what happened to the comic strip where openrc and runit battled systemd?
It was cropped and this is being passed off as new content
Now we just need to find a way to integrate systemd into wayland and watch people lose their mind.
It sort of is, the whole elogind thing.
In practice, what makes it so bad?
Bad usability, binary logs, crummy architecture.
It's new and different, and the Linux boomers who are still stuck on ALSA and ext2 hate it.
what are the better alternatives for ALSA and ext2 ?
PipeWire and btrfs
what is it? systemD is new?
When you entered the scene before epoch 0 I guess it is.
Everything else aside, my biggest gripes are with service control. Instead of just "service" they had to invent a new name that was super close to an existing function (systemctl vs sysctl) and reverse the switch order. (service sshd stop vs systemctl stop sshd.service)
Besides that, I absolutely hate that all the service configs are not in a standard location. Well, you get things like sshd.conf which are still in etc, but the systemctl configs are who knows where.
There are more important things to hate on with systemd, but I went for the superficial this time and I absolutely hate service management with systemd now.
wrt conf file location, they're only generally in /usr/lib/systemd, /etc/systemd, or /run/systemd. You can always find out what's getting read with systemctl cat <service-name>. Way easier to find stuff than with some other random programs imo, I've seen crap have default conf files in dumb places like /usr/share/<service-name>/lib/etc.
It's not evil. It's merely
and now RedHat's wunderkinder has moved onto Microsoft where he's a better fit. Ideally, we can go back to Linux again.
Simple.
As someone who ran security for an enterprise OS company, I can't see why there's any debate on this. Are we used to choosing comfy things despite the safety concerns, now, or just when Lennart shits them out?
Are we used to choosing comfy things despite [...] concerns
People have been choosing convenience above everything else for a while, personally I find that doing so is even glorified at times.
Poettering worked for Red Hat from 2008 to 2022.[2][3] He then joined Microsoft.
In 2017, Poettering received the Pwnie Award for Lamest Vendor Response to vulnerabilities reported in systemd.
This Mastodon stream from Lennart Poettering describes a sudo replacement β called run0 β that will be part of the upcoming systemd 256 release. It takes a rather different approach to the execution of privileged commands, avoiding the use of setuid (which he calls "SUID") permissions entirely.
Basically Microsoft bloat confirmed, everyone switch back to OpenRC lol
There is nothing wrong about it, also it's easy to use which is a plus to me
I've never really had issues with systemd, but I must say when I was setting up void I did really enjoy the runit init system π€·ββοΈ
This is high art.