I switched to Void ~2 months ago from NixOS, shortly after systemd made decisions that I could no longer stand behind. I was heavily integrated into NixOS, with both of my laptops, gaming desktop, and servers running it. I had already tried Gentoo, and while it's great, I didn't want to compile most things, and I wanted something simpler than OpenRC.
I finally looked closer at Void Linux and thought I'd give it a shot. I nuked NixOS on my laptops and desktop (something I probably spent 80+ hours configuring) to install Void. My initial concern was gaming, as most people say you "have to be on the latest of everything to game AAA!!" Well, lo and behold, I get the same performance, if not better, on Void than on NixOS unstable. Everything just works, and the system is extremely lean, simple, and fast.
I'm really just posting this to thank the maintainers of this amazing distribution and to give people in the future another opinion if they're concerned about gaming on Void. Hardware below :)
Desktop:
-
Ryzen 5 7600X
-
9060 XT 16GB
-
32GB DDR5
-
6.18.28_1
-
mesa-26.0.6_1
Laptops:
-
ThinkPad T14 G1
-
ThinkPad T14 G6 (later switched this to Artix as it has better battery life)
Hi there, I have a few stupid questions for the void community to help me with please!
I use niri with waybar, and have KDE plasma as my other DE. I have elogind, with turnstile managing a few user services. emptty is my login manager.
- I'm looking at following guideline to properly configure KDE apps and environment variables into niri, which advocates for creating a folder in
~/.config/environment.d/
- the guideline seems to have some systemd component dependencies - e.g. the running of
systemctl --user daemon-reexec
- would this still work with elogind? I suspect it would, right?
2. Alternatively, as far as I understand, I could set the environment variables in the emptty config. Is this correct? The downsides of this being, if I ever moved to a different display/login manager I'd have to change this.
3. I could globally set the environment variables in /etc/environment. The downside to this being that any separate users would have environment variables also changed.
