Linux

I'm personally running Artix with runit and things are fine so far, but as ChrisG pointed out, dinit is basically a drop-in replacement for systemd syntax-wise.

Although if you're on Artix, you'll need to enable Arch's [extra] and [multilib] repos or you'll run into dependency issues on some apps due to some packages not being available in the main Artix repos. I learned this when trying to install steam-native-runtime, there were some Python deps which weren't available in the main Artix repos, but that were available in the Arch repos, if I'm remembering right.

Also, I recommend enabling the unofficial [liquorix] repo in order to get a newer kernel with more frequent updates than what Artix provides in their repos, eg. the default and zen kernels in the Artix repos lag a bit behind the lqx kernel from the [liquorix] repo, and I still recommend enabling [chaotic-aur] as a convenience repo on any Arch distro.

I also switched to MATE from KDE out of concern that KDE could end up following GNOME's path after SDDM is deprecated, plus I just wanted a lighter and different desktop, that and MATE's default two-panel layout is completely usable from stock although you might wanna set the panels to auto-hide to maximize screen space.

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.

Systemd is fine. Stop getting trolled by antiquated neckbeards.

Unless you find a specific problem with something, don't go looking for reasons to fix that which is not broken.

The main functional difference between systemd and others is that systemd will just work. Others will require you hand tune and hand tinker with a non-mainstream Linux distro.

If your hobby is init systems by all means mess around though.

I personally quite like systemd. Unit files are clean, timers services and sockets are easy to manage etc.

Honestly it’s a non-problem. Best advice is to use what is best supported. Don’t let the extremely fringe (but loud) tiny group of systemd haters throw you off.

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.

it’s one of those cases where if you have to ask, you should probably just use systemd. anything else is outdated or a passion project based on some idealism, which i’m all for, but if you’re worried about gaming performance as a primary concern i’d put it out of your mind. for example, i’m an obsessive tinkerer that uses NixOS and Arch before that and i use nushell and Neovim and Hyprland, but i use systemd cuz i don’t see a reason not to. it’s well supported and stable.

Dinit for desktop, s6 for server.

Btw, why is systemd even a thing for server distros? Can't play none of it's strengths but it's fault's affect security and stability.

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.

If you are asking about "gaming compatibility" you should not switch to a non-systemd distro. You will end up going through extra hoops for zero benefit.

i actually like systemd. i'm not sure why I wouldn't want to use it.

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 using runit

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.

I have heard that systemd is "heavier" than alternatives. I haven't experienced that. I don't think gaming is impacted at all.

I use openrc on Gentoo for desktop. It requires some script hooks for things that expect systemd, but works quite well. I don't pay attention to it much, unless I'm writing an init script.

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 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,).

Systemd, systemd-boot, systemd-snapwn

Good stuff

Oh good, this again!

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'm using shepherd right now and i've used runit in the past. Shepherd is definitely a beast of its own since it's configured in guile scheme, but in the case of runit it just runs schell scripts and the commands are for the most part just as simple as systemd. I've seen people claim that some programs won't work without systemd but i've never come across something that didn't work.

Why you want to switch from systemd? I hate how complex it is, this age verification and that they're trying make make Linux more Windows like, but in that bad way (it's created by people who prefer Windows over Linux so yeah). But if your installation is working and don't have troubles then don't switch.

Switching to "alteratives" shouldn't affect gaming compatibility at all, cause you don't need any daemons to play your games (maybe if you want to host server or use vpn for multiplayer). Remember that systemd is not init system, but software suite which provide init system also. I think that systemd might use more resources than other solutions. Some software can rely on systemd, but when are you installing program from your system repositories it will work cause it's prepared to work if you're using solid Linux distro. I had situation on MX Linux that I downloaded Mullvad VPN from Mullvad's Debian repositories and it wasn't working, because of no systemd. Then I discovered that MX Linux have Mullvad VPN in own repositories and it worked. On every non-systemd Linux distro you can install elogind which is usually preinstalled and it also care about compatibility layer.

If we speak just about other init systems try what you like. My favourite is runit, but the most popular alternatives are OpenRC (this is what I usually using, even right now on laptop and PC) and sysvinit. sysvinit was terrible experience for me on Devuan, on MX Linux okay; OpenRC is just okay, but I have few reasons to hate it.

Systemd is used by the most of people so if something will screw up more people can help you and there's more tutorials on internet, also sometimes you need to tinker more on other init systems from my experience as systemd is more handholding. But using different init system will give important experience and learn you more how your system works.

If you're looking for non-systemd distros check MX Linux which is the really good system, also for not advanced users who just want to run their games. It's using sysvinit and you have GUI tools to control daemons.

I've been daily driving Slackware since the late 90s or early 00s (don't remember). There's no systemd, and no drama. I run KDE plasma 6, steam with proton, flatpak, rocm for AI shenanigans and whatever else I want. Even the rolling release is solid as a rock. There are dozens of us! And we're not all greybeards. I started going grey in high school, but I ate cookies for breakfast today because I'm both a grown ass man and a child.

Try OpenRC. It's pretty simple.

If you want the convenient features of systemd without the cancerous assimilation of the entire userland then dinit is recommended. OpenRC is a mature choice. Server folk seem to recommend S6 but I dont have enough personal use of it to verify.

• expect every response trying to provide useful info here to be drowned out by systemd brigading