anti-apXos
The /etc/resolv.conf issue is a classic example of the reason I personally don’t use or recommend runit.
Without dependency resolution there is always a racing condition involved – several software packages try to modify & manage the resolv.conf file
Maybe I don’t understand what you mean by dependency resolution in this case, but since runit services are just shell scripts can’t you build the “dependency resolution” into the service startup in the script itself?
As examples, the runit bluetooth and connman services depend on a system dbus, so the antix run scripts for those services have a line to confirm that the dbus service is started before they go on to start the actual bluetoothd/connmand daemons.
Similarly, I wrote a runit service script for keyd and initially found that it didn’t work because udev needs to have finished enumerating all the input devices before you can start the keyd daemon, so I just added a little until… loop in the run script that spins its wheels until the input devices are available and only then starts the keyd daemon.
"--"