You need to install live-config-runit, then refractasnapshot will install without complaint. It works. I've made snapshots with runit.

If/when you decide to use a git repo, there's git.devuan.org. You can have a personal account there that's separate from the devuan packages. I don't think there's any way to build personal packages on our infrastructure.

Looks nice!

Part 3: Pre-defined and user-defined pre-sets for the equalizer?     fsmithred ducks

To use apt with https, you must select a package mirror that supports https. Not all of them do. Find one on this list and use it in sources.list instead of deb.devuan.org.
https://pkgmaster.devuan.org/mirror_list.txt

I don't know how that works with a proxy or if it even matters.

Would that be a red heifer or a white buffalo calf? Not that it matters for this. I think I can change your user name. Send me the name you want using the email you used to register. I'll post back here to let you know if I was successful or not.

fsmithred at gmail dot com

Where do you see that a minimum microarchitecture level is required?

Follow is not really the right word - we use most of their packages without changing them. Only packages that require systemd are either excluded or forked to remove that dependency. When we say that devuan is debian without systemd, we mean it literally.

Oops! Thanks, I fixed the link.

Yeah, there's a slow and steady effort to reduce users' choices.

Yes, the number of banned and forked packages increases with each release. In the banned packages list, compare columns 1, 5, A, F and K for a visual representation of this. (Beowulf, Chimaera, Daedalus, Excalibur and Ceres)

I moved this post to the section that has the most pipewire discussions. There's also one in the Documentation section you might want to look at.

I can't explain how that's happening, but I can offer some possible workarounds.

You could just use one bootloader to boot both systems. Boot whichever bootloader to the system you want first and then run update-grub to add other installations to the boot menu. You need to make sure that os-prober is installed and enabled in /etc/default/grub first.

Sometimes devuan installer makes a debian directory in the efi partition. I'm not sure why that is, but it's possible to give unique names to the bootloaders. e.g. Boot the first system and run something like grub-install --bootloader-id=firstsystem && update-grub and then boot the other systems and do the same to give each a different name.

It's also possible that the uefi implementation on your motherboard does not follow standard uefi methods. That's very common. I have one that lets me change the order of the bootloaders through efibootmgr, but the order only lasts until I reboot. i.e. it doesn't really change it.

It's possible for packages to be pulled from the testing suite because of problems and the fixed version got into ceres too late to be included or possibly will migrate down in a week or two. Check the changelogs and bug reports for those packages and you might find an explanation.

I got the screenshot I wanted by installing on a laptop that has eth0 that does not work and wlan0 that does work.
https://get.refracta.org/files/misc/pro … mware.jpeg

This was an expert install of devuan_excalibur_6.0-20250605_amd64_netinstall.iso. I'm not sure if expert is necessary to get this firmware question.

I answered "no" to providing the firmware on external media and proceeded.
When it got to network detection and configuration, it only saw eth0. Since eth0 is broken, dhcp failed. I set it up manually and gave it a good local address.

When it came to setting up the package manager, I had to proceed without a mirror. While it was installing the base system, I switched to vt2 and saw that it was installing firmware-iwlwifi.

After the sofware install but before it installed grub bootloader, I opened a shell and tried to set up the wireless.
wlan0 did not show up with 'ip a'. I chrooted the installed system (in /target) and tried configuring wlan0 in /etc/network/interfaces. That didn't work. wpasupplicant was not installed. rfkill was not installed, so I couldn't see if the wireless card got switched off. That's when I gave up.

In past releases, the network setup saw the wireless hardware and let me choose whether to set up eth0 or wlan0. That didn't happen here. I'll pass this info on to the iso builder.

Reported here:
https://bugs.devuan.org/cgi/bugreport.cgi?bug=894