I recently found the Ly display manager, which I've honestly fallen in love with, but I'm not sure how to enable it. The Arch wiki article on display managers has instructions on enabling it, but obviously those instructions assume the use of Soystemd. How would one go about this on Obarun?

Also, unrelated, but I've been having issues with manually started daemons turning off for no good reason; particularly pulseaudio. I've tried the following command: 
# 66-enable pulseaudio
As well as a few other names for the daemon, but all returned that the source path was unable to be resolved (I assume that's because of the wrong name for the daemon). So I've defaulted to 
 $ pulseaudio --start
and/or 
$ pulseaudio --daemonize
However, the daemon will randomly stop; rendering me without audio until I start it again. So how do I actually get daemons to start by themselves and stay alive in S6/66?
Do you have user services running? A boot@ user tree ?

My other question is why use pulseaudio and not alsa? Do you have alsa-utils installed? What does alsamixer show when you hit F6? I suppose you have something you use that depends on pulseaudio, and for those there is AUR:apulse (I wish Eric or JM would adopt it as native to Obarun).

I remember the pain in the arch in trying to run pulsea.. and that it had to run as root and user to be functional, but that was ages ago.
fungal_net wroteDo you have user services running? A boot@ user tree ?
Honestly not sure how to check that. Also unsure about the trees in general, I haven't been able to find many resources on S6 configuration, most operations I've learnt reading posts here, and their manuals haven't been much help imo.
fungal_net wrote My other question is why use pulseaudio and not alsa? Do you have alsa-utils installed? What does alsamixer show when you hit F6? I suppose you have something you use that depends on pulseaudio, and for those there is AUR:apulse (I wish Eric or JM would adopt it as native to Obarun).

I remember the pain in the arch in trying to run pulsea.. and that it had to run as root and user to be functional, but that was ages ago.
The only reason I have pulseaudio is since I couldn't get it to work with my headphone's usb dac. Regardless, I use the "nosystemd" variant/s from the aur
https://wiki.obarun.org/doku.php?id=dbus_and_dm
https://wiki.obarun.org/doku.php?id=66intro

Essential reading, you must first read about 66 then go to s6. The reason that 66 was made is so you don't have to become an expert on s6. s6 may take years of studying to understand, it may take weeks to get it going/running. 66 just makes it all reachable by the general user population. The other approach is the Artix way, reduce s6 to something primitive like runit, and make it run like runit, and get it over with. That is not why s6 was created, to be just another runit/daemontools fork.
fungal_net wrotehttps://wiki.obarun.org/doku.php?id=dbus_and_dm
https://wiki.obarun.org/doku.php?id=66intro

Essential reading, you must first read about 66 then go to s6. The reason that 66 was made is so you don't have to become an expert on s6. s6 may take years of studying to understand, it may take weeks to get it going/running. 66 just makes it all reachable by the general user population. The other approach is the Artix way, reduce s6 to something primitive like runit, and make it run like runit, and get it over with. That is not why s6 was created, to be just another runit/daemontools fork.
Thank you, this is exactly what I've been looking for.
The rest of the 66 documenation resides on a place of its own in the top right corner labeled software. Anything more specific than this ask Eric here or on that chatroom on NSA's irc channel.
Also,all tools have manpages ;)

Powered by Obarun