It's now been forked and called vstbridge. It can be found here  https://sourceforge.net/projects/vstbridge/

I do not which ones of my runit scripts could be of use, since let's be honest, most of them are a dead simple. The process is dead simple: read the daemon's manual, search for the word: "PID", "fork", "background", "syslog"... this kind of stuff. Note the option that allows to disable those "features". Usually, it means running in what the author call "debug mode", and write your one-liner...

There are few exceptions, though, the most notable one being the cursed udevd. This is technically NOT my script, at least the ugly trick is something I've found like 10 years ago on some random blog post. I do not want to claim I did it, but this really helped me back then and I am unable to find anew the original author. I have integrated it along my system, as well, so I modified it a tiny bit.

DISCLAIMER: my computers are a mess, and I have several variants of some of those scripts, for random and idiotic reasons. Some are cleaner than others... I've been carrying those things since a decade, after all.

Here is the /etc/sv/udev cursed script, adapted to devuan (because debian ofc can't refrain shuffling files randomly every major version they do, and devuan fixed that toward the sane way... /complains):

#!/bin/sh

. /etc/runit/common

need()
{
	i=0
	while ! test -e "$1"
	do
		sleep "0.$i"
		test "$i" = 9 || i=$((i+1))
	done
}

mkdir -p /run/udev
rm -f /run/udev/control #just in case
rm -f /run/udevd_ready #just in case
(
	need /run/udev/control # not sure we really need to wait for it
	echo "Trigger+settle:"
	udevadm --debug trigger --type=subsystems --action=add
	udevadm --debug trigger --type=devices --action=add
	udevadm --debug settle
	>/run/udevd_ready
	echo "Done: trigger+settle"
) &

echo "Starting $SVNAME"
exec env - PATH="$PATH" /usr/sbin/udevd -N late

It starts, like all my runit scripts, by sourcing a single, trivial script I name /etc/runit/common:

#!/bin/sh

#this file provides some automatic features for runit daemons
#notably it:
#* provides the variable SVNAME, which is the name of the daemon dir
#* provides the die() function
#* sources an existing ./conf file
#* automatically rotates logs on startup if there are logs and AUTO_ROTATE=yes
#* redirects stderr to stdout
#* enables some shell verbosity and safeties (-xe)

die()
{
  printf "%s\n" "$@" | tee ./down
  exit 1
}

SVNAME="$(basename $(pwd))"
HAS_LOG="$(test -d "$(pwd)/log" && printf "yes")"
exec 0<&-
exec 2>&1
set -xe
test -f conf && . ./conf

if test "$0" = "run"
then
  if test "$SVNAME" = "log"
  then
    SVLOG="$(basename $(dirname $(pwd)))"
    SVNAME="${SVLOG}/${SVNAME}"
    AUTO_ROTATE="${AUTO_ROTATE:="no"}"
  fi  
  test "yes" = "${AUTO_ROTATE}" -a "yes" = "$HAS_LOG" && \
    sv alarm "$(pwd)/log"
fi

I also have a generic logger, so when I create a new service, I only create the log dir, and symlink it as "run", so it's named /etc/runit/log.run:

#!/bin/sh

SVLOG="$(basename $(dirname $(pwd)))"
LOG_PATH="/var/log/$SVLOG"
test -e "$LOG_PATH" || install -d -m 0750 -o root -g adm "$LOG_PATH"
exec svlogd -tt "$LOG_PATH"

I also have /etc/runit/global.finish which does not do much:

#!/bin/sh

. /etc/runit/common

echo "Stopped $SVNAME"

Maybe my networking stuff may be of interest, as I do not use ifupdown, networkd or whatever...

#!/bin/sh

. /etc/runit/common

ip l set $IFACE up
if test -e /sbin/ethtool
then
	while $(/sbin/ethtool $IFACE | grep -q 'Link detected: no')
	do
		test "$VERBOSE" = "yes" && echo "$IFACE unplugged, sleep ${SLEEP:=60}"
		sleep ${SLEEP:=60}
	done
fi

echo "Starting $SVNAME on $IFACE"
exec udhcpc -i $IFACE -f -R -n

This stuff is not worth much, but apparently nothing does that kind of things in devuan? Or I could not find it, which seems more likely. I've been using those (or slight modifications, I do that for my own user, too, and similarly adjust the stuff on my toy server, and used to have a 250+ fleet of street equipments at work) since more than 10 years, as said, and this requires zero maintenance. I'm a lazy person, and thus runit have kept me happy for long. I'm expecting this happiness to last, because it's a sane program, which can handle whatever I want with just few lines of shell.

The logic behind the finish and even the starting is that it makes it dead simple, when reading your logs, to know when the daemon actually started and ended. Which I have found to be extremely useful, but YMMV. I would never remove those from system, clearly, but it's not really orthodox, I suppose.

That's it. I have a lot more runit stuff, on my systems, the only stuff which are not migrated are the services which do not spawn a daemon, mostly out of lazyness.

https://github.com/WeirdGnome/AppImage-Installer

Btw, at present my .asoundrc says this:

pcm.!default {
        type sndio
}

I wonder if its possible to enable both cards at the same time.  It would be peculiar though.

Deb package to follow soon, this is very new and testing is just getting started.

The general consent seems to be: Don't do it!

And I will not.

Maybe I'll try a VM or a disposable installation sometime.

The suggested deadbeaf deb-package form sourceforge works so far on freia. Main reason to install it were two plugins: "musical-spectrum" for spectral lines by notes and "spectrogram", which draws a logarithmic sonogram (impressiv, if you like such things).

Intersting to hear that some distributions officially include deb-multimedia.
Also will keep in mind to eventually pick isolated packages by having the repo temporarily enabled.

Again, thanks for the detailed posts.

shed v0.3.0 is finally out, all tweaks and last minute changes were made so that it would still
release on May 14 at least in UTC -0600...

anyway, go have fun setting up shed on your system, i'll try to cobble a package through the
weekend, once i got something that builds with debian tooling i'll look to get the package on
debian, ought to wonder if the people working on init diversity would be interested in shed or
they'll prefer to invest into another solution, regardless now i can look on ways to get the
ball rolling.

Just for giggles I tried it on Mate last night and yeah it installed fine and worked great up until I hit that Apply button...it was a hoot, it actually tried to apply the paper but only like a quarter of it laid over the previous wallpaper.

Downloading the iso you linked to now, will try this in a live-session and see what's what.

EDIT: Well I got sidetracked yesterday and didn't get it done, but just finished downloading it a minute ago, let me get a little more coffee in me and i'll get started, never used anything Void-based so this will be fun for me, I do like exploring new file systems to see how they work.

EDIT: I don't know why the pics are blurry but the app is nice and sharp actually, lol.
EDIT2: VuuPew is an acronym, it stands for "Veteran Unix User's Projectile Estimation Widget", my wife came up with that name, I think it's brilliant.
EDIT3 3-29-2026 : Added wind drift but my math is still off a bit, got everything else done and the save function puts out a great simple printable chart + notes and details, updating the screenie below.

Note that I included a .desktop for the standard version in case you want to do a full manual install, but there's not one for the portable version, it doesn't need one, just drop the binary on a USB stick and click it to run, it will do the rest.

It probably goes without saying but you need gtk3 and libsodium onboard to run it.

https://sourceforge.net/projects/vuu-do … s/VuuPass/

Remember, this is first test of experimental software, test only with dummy data for now until more test results come in.

Welp, w/e.