runit-services VS Steam-Deck-Guide

I did some digging and found this repository with some examples for runit scripts, but they needed a little bit of adjusting; specifically they make use of the deprecated pipewire-media-session. After adjusting them, I symlinked them in to my runsvdir and … still nothing! At this point, I almost decided to just go back to the shell script and let it go, but the next day I was picking at the problem again and found that the approach for per-user services as described in the void docs puts your user services into an environment that is isolated from your user session. You can take a look at the env of a process in htop, and if you look at any of your usual user-processes you'll probably see a long list of environment variables, but the user-level runsv process started by the system-level runit only knows about the variables you export in /etc/sv/runsvdir-your-username/run like HOME and USER. This effectively hamstrings services that need to run like other "normal" user processes.

git clone https://github.com/madand/runit-services cd runit-services sudo mv psd /etc/sv/ sudo ln -s /etc/sv/psd /var/service/ sudo chmod +x etc/sv/psd/*

Accessories

Awesome. You should consider adding anything new to this: https://github.com/mikeroyal/Steam-Deck-Guide

I love awesome pages on github, and I prefer a curated, simpler version this in awesome style.

Someone posted a guide they were working on in github which I really liked (https://github.com/mikeroyal/Steam-Deck-Guide). Since seeing that I've been expanding on and trying to reformat it in my own fork which I occasionally pr. My fork is https://github.com/NullStuff/Steam-Deck-Guide. Both provide a lot of information.

- This Guide has lots of interesting links

For now the most comprehensive one I found is this one https://github.com/mikeroyal/Steam-Deck-Guide