I fired up the antix full runit iso. Here's a list of runscripts they have that are not in Lorenzo's collection. This is as far as I've gotten with it. I haven't tried any of these yet or even looked inside the files.

AntiX has:
bluetooth, connman, ntp, ofono, rpcbind, rsync,
rsyslog, smartmontools, tlp, udevd, ufw

Back in June I posted in this thread and said there needs to be a live-config-runit package. Well, now there is. I forked live-config. The version currently in ceres includes live-config-runit. (11.0.2-1+devuan2). It will move into chimaera soon.

IMPORTANT NOTE:  If you have live-config installed, when you try to install runit-init, apt will want to remove live-config (and refractasnapshot, if that's installed.) The way to get around this is to include live-config-runit in the command to install runit-init.

For beowulf, I just made an easy single live-config-runit package that isn't in the repo. You can get that here: http://distro.ibiblio.org/refracta/file … u1_all.deb  Install it before you try to install live-config and after you install runit. (i.e. stuff might get put on the autoremove list. Just reinstall things if you need to.)

Another note: I did not replace the live-config init script with a run script. That's a project for a later date.

You're right. I just tried this in chimaera with mate. It also does it in beowulf with xfce and the cinnabar theme. Maybe we can figure out how adwaita does it and do the same in our themes.

There were no new packages in chimaera for a couple of days, and now there are. I think it's possible that there really were no new packages. Buster is in freeze, so the changes should be slowing down.

I found the problem in the minimal-live. The fix is:

apt update
apt remove librsvg2-2
apt install librsvg2-2

That will drop the version from 2.44.10-2.1+deb10u3 to 2.44.10-2.1. And then you can install firefox-esr and the other stuff.

The problem is that the build process pulled in librsvg2-2 from beowulf-proposed-updates, but then that repo was removed from sources.list. I'll have to make a new set of isos.

Berni, if your last post is after a netinstall, then there may be another problem, too.

I wanted to be able to boot to console on occasion. With sysvinit, I just turn off the display manager in runlevel 3 and put a '3' in the boot command when I want that. It's pretty easy to make a new runlevel in runit.

1. Create a directory in /etc/runit/runsvdir/ named for the new runlevel. Check man pages for the reserved names.
2. Populate it with symlinks to services in /etc/sv/
3. Change to that runlevel with a command or boot to that runlevel with a directive in the boot command.

I did it like this and got the symlinks right without having to make them all manually or script it.

cd /etc/runit/runsvdir
mkdir testt
cp -a default/* testt/
rm testt/lightdm

Add this to the linux line of a boot entry to be able to boot to the new runlevel:

runitdir=testt

This is working correctly.

To change to the new runlevel after a default boot:

runsvchdir testt

This isn't working for my example. It drops to a black screen with a blinking cursor, and I'm in a VM window, so I can't switch tty. It does work when changing to the default runlevel after booting to console.

I just built the package. It's in the ceres repo and will propagate to mirrors in the next few hours. Then it will move into chimaera in a week, I think. Note that this is only the desktop window theme and doesn't even include the desktop background image.

Note2: There's an earlier version I built a month ago. If you already installed that, it'll get upgraded to the new version when the new one moves down. Ignore the big jump in version numbers. That has nothing to do with the extent of the changes between the versions.

It's here if you absolutely can't wait.
https://pkgmaster.devuan.org/devuan/poo … -1_all.deb

I just booted a live iso in qemu and installed vbox. I had to say those words in my head before I realized how weird it is. Anyway, I got the same error messages as you. Before I did it, I checked in sysv-rc-conf to see where dbus starts, and it starts in 2-5, not S. I checked beowulf, ascii, chimaera, jessie and wheezy. All the same.

There's no mention of dbus in /etc/init.d/vbox* or /var/lib/dpkg/info/virualbox-6.1.* so I don't know where that message is coming from.

I don't have any ideas for the usb. Yes I do. Not a fix; just a workaround. Someone I know used shared folders with a usb mounted on the host system.

I have not read any accounts of anyone migrating from devuan to debian or other debian-based systemd distro. You would be cutting a new trail.

Obviously, you would need to add a mint or debian repo to your sources to install banned packages. You might need to do some creative pinning to prevent a disaster. Either that or do a full migration back to LMDE. Please write it up if you do. Thanks. Good luck.

Cool! Please tell us a little about what desktop environment and display (login) manager is installed. And if you have autologin set for your installed system, please describe how you did that. The live-config scripts set up autologin for the live environment. Maybe two settings are competing.

Optional: At the isolinux boot menu, press TAB to edit the boot line and add the one word, noautologin. And see if it boots to a login screen. Or maybe it'll boot to desktop.

One thing that might help is to edit /etc/refractasnapshot.conf to set save_work="yes". Normally, the copy of the filesystem gets deleted after the snapshot.iso is made. If the work dir is not deleted, we can do some forensic inspection and some other tricks, maybe.

Also...
I did not see any indication of a common problem in the log file you sent me, but looking again at your df output has me wondering if you're running out of space. You posted:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       8.6G  4.0G  4.2G  49% /
/dev/sda2       8.5G  3.0G  5.0G  38% /home
/dev/sda6       247G   98G  138G  42% /media/data

I see 4G of operating system plus 3G of home used. That's a total of 7G unless you added a bunch of stuff to the excludes file. I'm guessing you did not do that. Refractasnapshot makes a copy of the entire system (minus what's listed in the excludes file) and puts that copy in /home/snapshot. But you only have 5G free space in /home.

You can switch the location of work_dir and snapshot_dir in the config file. Change this:

snapshot_dir="/home/snapshot"
work_dir="/home/work"
efi_work="${work_dir}/efi-files"

  To this:

snapshot_dir="/media/data/snapshot"
work_dir="/media/data/work"
efi_work="${work_dir}/efi-files"

Then run refractasnapshot.

The prefix is hard-coded in grub-efi-amd64-signed. I'm not sure what changed in this last update. I first ran into this problem a year ago. If you remove the signed package and just keep grub-efi-amd64 it should fix the problem. Usually. And not if you need to use secure boot.