What are some significant differences to expect when switching to an alternative, and can that affect gaming compatibility and performance?
I use systemd it’s fine and requires very little extra thought.
If you have to ask this, then its probably good idea to stick to systemd. I don’t see any reason to change, other than to protest. In the process doing so you will probably encounter issues. People switch away from systemd for various reasons, but not for performance. In example they don’t like who develops and controls systemd. And they don’t like that it does more than just initializing the system, as bunch of other tasks are bundled into it. If all of that does not bother you, stay with systemd in my opinion.
And if you really want to switch to systemd, then I recommend to use a dedicated operating system (a distro) with that in mind. Don’t forget, that systemd has many features and services, that its expected as a standard. You do not just change an init system, but replace all other components too.
do you think you’ll continue to use sysemd once it start embracing gov’t id requirements to use it?
i ask because i hold a similar position, but it’s adoption of the first step towards this end goal has me wondering if i should start looking for an alternative.
The developers of systemd said they will never support that, so I think its safe for now. Also why do you think systemd would “require” a government id check? systemd is just providing the functionality; it is the distribution / operating system that implements all the functionality. So if an operating system does implement it, I might find a different operating system, regardless of if it uses systemd or not. That is true for any other component too, not just systemd.
a government id requirement is the next logical step after its needful framework has been built as a result of the age verification laws that have already taken affect in the uk and california.
and because it’s a government law, it’s out of the systemd developer’s hands. linux is influenced heavily (if not outright controlled) by corporations like red hat who have to abide by the law if they want to continue operating and, in a likewise fashion, the systemd maintainers must also comport themselves if they want systemd to remain the dejour method that linux uses to initiate itself in those ecospheres.
That is speculation. And as said, its not the decision of systemd to implement that, it is a decision of the operating system / distribution. I live outside the areas of those laws. What the next logical step is, is open to interpretation and that is not what I am discussing here.
OpenRC here, on Gentoo.
It works pretty well, fast and simple, honestly I never felt the need for SystemD.
I use the latter at work sometimes, I don’t really like how it changed the way stuff works, but I have nothing against it. I just feel the extra complexity is not needed in all of my home setups (laptops, servers, etc). So it’s OpenRC everywhere for me.
Except for systems with very limited resources, systemd or not won’t make much of a difference in performance. A lot of tutorials on reading system logs and managing background services will assume that you are using systemd.
I’ve only ever used distros with systemd, not necessarily with intent, but because it was the default and well-supported. Probably won’t switch unless
- Debian switches
- there’s a change that breaks my workflow
- it somehow starts phoning home to a big datacenter.
I’m switching to GuixSD. Fortunately I have an old laptop and can build up my system there until I feel confident enough to do the real switch.
Pros I have encountered so far: booting in 20 seconds. Nice, although small, community. Scheme is cool. When the time comes, I will just need to copy two text files (and my dotfiles) to the main laptop, and my system will be (theoretically) the same, and it will be (theoretically) unfuckable.
Cons I have encountered so far: some kinks that were quick to research and fix while on an Arch-based distro, now are a bit more of a pain (but most of them in the fun way at least). For now I have given up trying to make the Thunar archive plugin work and switched to PCmanFM. Also I had to install Logseq as a flatpak. I have started very recently and I have not installed much yet so no idea about the impact on gaming.
ETA: there’s !guix@lemmy.ml and !guix@infosec.pub on Lemmy.
i actually like systemd. i’m not sure why I wouldn’t want to use it.
Age verification? How about their attempt, after taking over udev development, to drop support for other init systems to force people to use systemd? It’s track record of security flaws?
Filesystem enable age verification in pretty much the same way as systemd does: You can optionally store a user’s birthday. That is such a ridiculous statement.
To be fair: None of the other inits cared for udev. None contributed or helped by providing features they wanted to improve udev. The systemd devs care for the lower level plumbing overall… and not just for the init system. So it is very natural for low level plumbing projects to land under the systemd umbrella today.
Systemds track record wrt. security flaws is actually pretty good. Not many went through the cracks,maven though some were indeed pretty ghastly. Hardly any was in the core functionality, most were in new code not widely used yet.
On the other hand, the service hardening that systemd enables has improved the overall security of a typical Linux system by quite a lot.
Dinit for desktop, s6 for server.
Btw, why is systemd even a thing for server distros?
Dinit for desktop, s6 for server.
What is wrong with s6 for desktop?
I find how it works, with the database compiling, is more suited for stable and reliable than for Desktop with always changing conditions.
Systemd, systemd-boot, systemd-snapwn
Good stuff
I use OpenRC on most of my systems, which honestly works well enough that I’ve never felt the need to change. SystemD at work though, which is also fine. If I have any complaints, it’s just not what I’m used to.
Switching could be tricky, and may not be worth the hassle. It’d really depend on what you want to get out of it. As always though it’d be a good way to learn as you’ll inevitably break something and need to figure out how to fix it.
If you use your computer for gaming, probably best to stick to well known/supported (in theory it shouldn’t matter, in practice if you are asking this you really shouldn’t).
I would say the big thing that might give you trouble is not the init system, but NetworkManager. NetworkManager is the… network management software (wow who woulda guessed?) used on desktop linux distros.
People have many criticisms of it, that are similar to criticisms applied to systemd (it’s also Red Hat software), so I see my friends switching to iwd, wpa_supplicant, or other alternatives when trying something other than systemd as well.
It gives them a lot of pain. None of the other alternatives are as reliable as NetworkManager when it comes to connecting to Wifi. Switching away from Systemd shouldn’t be too hard, but NetworkManager is much tougher to give up. Thankfully, you can run NetworkManager on non-systemd setups.
I’ve not had any gaming issues. The only real perfmance impact is boot time (which can be better or worse than systemd). The future I hope for is dinit with turnstiled. dinit is really quite nice. But openRC also works quite nicely. Unless you wish to excessively engage with system services, none of it makes that much of a difference. The real difference in usability is in how well everything is packaged and maintained (which is why openRC on gentoo is great for example,).
deleted by creator
Runit is softly better but Systemd is perfectly fine. I would prioritize runit on very old hardware.
I’m currently using
systemd, but have been strongly contemplating a migration to Void, which would have me usingrunitI installed Void on my laptop to learn it, loving it so far.
On my gaming desktop I’m using Devuan, but I have room for additional distros so I’ll definitely dual-boot Void as soon as I feel confident with the basics.
