Sometimes questions about refracta tools appear in the Derivatives section, sometimes in DIY and sometimes in Installation. You have my attention, so right here will also work.

Here's the documentation for it:
https://refracta.org/docs/readme.refractasnapshot.txt
https://refracta.org/docs/refractasnapshot.conf.txt
https://refracta.org/docs/snapshot_exclude.list.txt

You can load it to ram when you boot from dvd or usb. If you must run from dvd, I strongly suggest that you boot it to ram. It takes a lot longer to boot that way, but then it responds much faster while you are using it. Running from usb is almost as fast as running from hard drive, so you might not feel the need to boot to ram.

Running a program in firejail prevents the program from accessing any directories that are not specified in the profile for that program. For example, my firefox can only see the Downloads directory. I cannot access any other files in my home from within firefox, and neither can any of the websites I visit.

deb10u1 in the version means first revision for debian 10, which is buster, which is also beowulf. Decide whether you're running ascii or beowulf and stick to one. Let us know what you put in sources.list.d, too.

I sometimes do the opposite and search for debian when I want devuan, because there's a better chance of getting useful hits on a lot of topics.

I can't give you a time estimate on when or if s6 will be a choice during installation. I've heard nothing about it in months.

The point-release of beowulf will add runit to the init system selection in the installer. Maybe s6 can be added in time for Chimaera. That's a guess.

Boot with live-iso, shrink the /boot partition and make a new partition. Do not format the new partition with a filesystem. (Unformatted is the last choice in gparted's dropdown list of formats.) Give it bios_grub flag (or type ef02 if you use gdisk).

You need at least 1MB for the bios_grub partition. I usually give it 2MB so I don't have to worry about what kind of MB I'm using.

That's my current key and it has a good signature here. MIT's pgp is frequently down. I just tried to get my key in a web browser, and it failed to find it. Never mind that I uploaded it to pgp.mit.edu when I created it.

Try subkeys.pgp.net and try refreshing your keys. Last year I updated the expiration date on the key but it didn't get updated on the keyserver until later. (mit was down at the time)

Using --refresh-keys will update your local copy.

Do you happen to know what command that executes? If not, we should figure that out. What terminal is it, what desktop environment are you running? Maybe a right-click on that icon will let you see a list of Properties that will show the command.

Does the error message appear inside the terminal that you just opened, or is it in a notification window or other popup?

If you have a terminal that will let you run commands, run the command that the panel icon uses to open a terminal and see if it gives you any more information.

Maintainers Guides
https://git.devuan.org/devuan/documenta … aintainers

The error message is coming from bash - the command providing the error is the first word in the error message. You get 'command not found' if ash is not installed. If you're sure you installed it, then something weird is going on or you didn't notice when it got removed.

If you create an empty /bin/ash, you should then get 'permission denied' because it's not executable. If you make it executable, then the error messages go away, but of course it does nothing.

A few messages above, you said 'ash' gives you a root shell after aliasing 'su'. The prompt that you pasted is a bash prompt. The ash prompt is just # or $ for root or user, respectively.

Note: You can also get 'command not found' with the new default su setup if the command you're trying to run is in an sbin directory and you used 'su' instead of 'su -'. Your alias works around this.

I would not boot that system again. Check it from another system, maybe a live-CD or live-USB.

You might want to run from live media from now on, so that you have a read-only system. That way if someone is able to install software on your system while you are running, you can just reboot to go back to the clean state. And figure out how to keep them from doing that. To save files, you can either set up a persistent volume or plug in another usb stick.

Some of your questions are answered in the release notes. (grub, su)

You can run without any policykit or dbus, but removing /etc/pam.d/ might have been a bad idea. This link is provided for general information. You don't want to use the nodbus isos I made because they are not secure. (ssh is running and the password is public)
https://dev1galaxy.org/viewtopic.php?id=2158

Install libpam-elogind