We do not fork the debian kernel. If you have issues with it, you should direct your complaints to debian or possibly to kernel.org. Not here.

To answer your question, I don't think you need to do anything special to use refractainstaller in ubuntu, but to use refractasnapshot you need to change the initrd compression to xz. When the next version of refractasnapshot is released, you won't need to use xz compression. The new version will support zstd compression.

Another solution is to use mmdebootstrap which does a better job of handling the dependencies. It will install systemd-standalone-sysusers before cron-daemon-common.

On my daedalus system, aptitude says it will install ceph and cephadm. How did you determine that it requires systemd?

If apt or apt-get won't let you install it, please post the terminal output so we can see what's wrong. Also, if you try it with aptitiude, you might be given some alternate solutions.

apt show ceph*

Will give you information about every package whose name starts with ceph. None of them depend on systemd.  One thing I'm not clear on is whether docker containers work in devuan.

It's pretty much the same as before. The iInstructions for upgading devuan chimaera to daedalus are relevant. Note that firmware is now in a new section called non-free-firmware and add that to sources.list if needed.
https://www.devuan.org/os/documentation … o-daedalus

From the linked post with minor changes (version, sysctl.conf and lvm.conf). (General rule: take the new ones if they are different. Add or edit as needed.

I ran into the same problem a few days ago. The upgrade to 6.6.9 kernel and adding the usrmerge package (I forget which order I did them) broke it. I could still boot the 6.5 kernel, but I couldn't get to the desktop. Some files for lvm2 and dmsetup were missing. In several stages, I reinstalled lvm2 dmsetup, xorg, xserver-xorg* (whatever was installed) and xinit, but I still couldn't use startx or lightdm. I reinstalled elogind libpam-elogind and policykit-1-gnome and that fixed it. (at least I think the last thing I did fixed it.)

I was about to ask you the same thing. So I asked the Duck instead, and top choices seem to be PeaZip (not in debian/devuan) or Engrampa.

On my full-desktop xfce system, engrampa wants to add 15mb and file-roller wants to add 21. Ark wants to add 200mb, but that's because it needs a lot of qt stuff that isn't installed. On my minimal lxqt system, ark wants 90mb, lxqt-archiver wants 7mb, xarchiver wants 1.7mb.

If you feel like testing, here's a modified refractasnapshot script that handles editing the initramfs better. I've tested it in a VM with encrypted lvm and then again in the same system after adding amd64-microcode and intel-microcode. I did this in daedalus, which is using zstd compression for the initramfs. Seems to work fine.

Copy the file, make it executable and run it from your current directory:

sudo ./refractasnapshot -d

(or as root without the sudo)
https://git.devuan.org/devuan/refractas … tasnapshot

Just because someone posts something on the devuan forum does not make it the official word of devuan. Users get to speak for themselves.

I'm confused about what the problem is with your computer. You said you installed the latest Refracta, but then you're talking about kernels 6.5 and 6.6. The latest Refracta release is based on Devuan Daedalus, and it has a 6.1 kernel. I see that daedalus-backports has a 6.5 kernel but not a 6.6 kernel, so maybe the reason the 6.6 kernel doesn't work is because it wasn't built for the release that you're running.

The Refracta iso not booting in VM is weird. Check the sha256sum to make sure the download was good. But that doesn't explain the other failures.

The script output suggests that you have a resume file in your initramfs. (remove_resume=yes) but I don't see a corresponding 'rm -f ...resume' in the section under "edit_initrd".  Run lsinitramfs | grep resume $initrd where $initrd is the full path to the initrd in the excalibur iso. If you mount the iso, it will be in $mountpoint/live/initrd.img. Or you could retrieve it from the build host (assuming you set save_work=yes in refractasnapshot.conf). It would be in /home/work/iso/live/initrd.img.

You could also look in the build system for /etc/initramfs-tools/conf.d/resume and see what's in it. If it exists, make sure it says RESUME=none inside or delete it, and then run update-initramfs -u You only need the resume file if you want to resume from disk hibernation, and you usually don't want that in your snapshot.

Are you using a custom kernel? If so, compare your kernel config file to the one for the stock kernel to see if something is missing.

It may be something in the way the isos were made. I boot isos in qemu and vbox all the time. The only thing that doesn't work well is if the VM is set to do a uefi boot. In that case, I have to go into the efi setup and find the actual file to boot.

Take a look at /var/log/refractasnapshot.log or let me look at it.

Hi and welcome to Devuan!

We only have around a dozen people maintaining forked packages, and that load keeps getting bigger. If you ever get the urge to start developing again, it would probably be easy for you to find something to do around here.

From what I've seen, migrations from debian to devuan are a crap-shoot. I think it depends on what all you have installed. Upgrades and fresh installs are a lot more reliable.

In general, I think devuan is more like debian than debian is. I think you'll feel at home here.