Just my two cents: FDE works fine when pre-partitioning with a GParted Live and manual partitioning in the installer. Valid all along from ASCII to Daedalus.

Just to make you fully aware: Devuan is nothing but a Debian deriviate. It makes sure you have init freedom, i.e. you can simply use the same kind of routines that did exist before Jessie and systemd introduction, and that you are NOT forced to use systemd. Inits supported like sysvinit, openrc, runit, ... All the rest of the SW is Debian, like this usrmerge topic. Too much to convert back by the small Devuan team.

I am absolutely happy that I have found Devuan, and that I can use the same kind of procedures to encrypt and decrypt my installations as used back in Etch, Lenny, Squeeze, Wheezy.

Make sure you understand who is responsible for what ... you are wasting your and our time here.

... and NOT a Devuan invention ...

Well, I am working with LightDM/Mate re. Cinnamon. I myself had some trouble getting ASCII to work with consolekit, the elogind stuff fixed that. And that is what I copied into my reply.

When I do an apt list on my Daedalus I get:

# apt list libpolkit*
Auflistung… Fertig
libpolkit-agent-1-0-dbgsym/stable 122-3devuan1 amd64
libpolkit-agent-1-0-dbgsym/stable 122-3devuan1 i386
libpolkit-agent-1-0/stable,now 122-3devuan1 amd64  [Installiert,automatisch]
libpolkit-agent-1-0/stable 122-3devuan1 i386
libpolkit-agent-1-dev/stable 122-3devuan1 amd64
libpolkit-agent-1-dev/stable 122-3devuan1 i386
libpolkit-gobject-1-0/stable,stable,now 122-3devuan1 all  [Installiert,automatisch]
libpolkit-gobject-1-dev/stable,stable 122-3devuan1 all
libpolkit-gobject-consolekit-1-0-dbgsym/stable 122-3devuan1 amd64
libpolkit-gobject-consolekit-1-0-dbgsym/stable 122-3devuan1 i386
libpolkit-gobject-consolekit-1-0/stable 122-3devuan1 amd64
libpolkit-gobject-consolekit-1-0/stable 122-3devuan1 i386
libpolkit-gobject-consolekit-1-dev/stable 122-3devuan1 amd64
libpolkit-gobject-consolekit-1-dev/stable 122-3devuan1 i386
libpolkit-gobject-elogind-1-0-dbgsym/stable 122-3devuan1 amd64
libpolkit-gobject-elogind-1-0-dbgsym/stable 122-3devuan1 i386
libpolkit-gobject-elogind-1-0/stable,now 122-3devuan1 amd64  [Installiert,automatisch]
libpolkit-gobject-elogind-1-0/stable 122-3devuan1 i386
libpolkit-gobject-elogind-1-dev/stable 122-3devuan1 amd64
libpolkit-gobject-elogind-1-dev/stable 122-3devuan1 i386
libpolkit-qt5-1-1/stable,now 0.114.0-2 amd64  [Installiert,automatisch]
libpolkit-qt5-1-1/stable 0.114.0-2 i386
libpolkit-qt5-1-dev/stable 0.114.0-2 amd64
libpolkit-qt5-1-dev/stable 0.114.0-2 i386

Looks like the backend stuff is gone, don't know when, and apt list *backend* confirmed that.

Give the first part a try, it should replace the consolekit stuff.

The solution is to wait for the solution ..... Have you raised a bug report? It may be fixed in the future.

The solution will come some day.

Well apt policy did not show the 32 bit version. Give

# apt list libcrypt1 -a 

a try.

Normally the 32bit version cab be installed by:

# apt install libcrypt1:i386

According to the help dialogue system-config-printer is an old RedHat development. Its a tool for cups.

I like it the way it is. I want it locked to avoid that any user can modify settings and then complain that the printer does not work. Its an admin tool.

I am not aware about any configuration option that allows to remove the root password. I am not familiar with MX Linux. Maybe they have used a policy to remove the need for a password entry? Have a look at /usr/share/polkit-1/actions (Debian path).

To set some minds right in terms of relations between Debian and Devuan: The small Devuan team just replaces a minimum set of packages related to systemd by packages that support init freedom. The Devuan web page (accessible by a link on the top of this page) amongst other information also shows a list of banned packages. Only these are modified or replaced.

All the rest is a 1:1 copy of the Debian repo.

This is also true for Firefox. What isn't in the Debian repo can't be found in the Devuan repo, no matter if on cli e.g. by apt or in graphics mode e.g. by Synaptic.

This libhcrypto.so.4 has something to do with Heimdahl stuff. Maybe that's a hint ...

Can't exactly remember what I did several months ago when reading in some W98SE floppies with an USB floppy drive.

Some ideas:

Make sure you are in the floppy group.
Install mtools and dosfstools.

Then reboot and give it another try.

You should install fuse3. But you will have to remove jmtpfs, that conflicts with fuse3.

Yes it can.

Size: my suggestion is 1024 MiB to avoid any issues with strange EFI bios implementations that would like to use the ESP as storage for firmware updates. Minimalists call this way too large. The size is an insurance against the unforeseen.

Filesystem: FAT32/vfat is a must.

If no other ESP is present, create a new one.

If there is an ESP in place already, no need to create a second one. It will not be overwritten or getting damaged. You need to make sure its added in the list of partitions as ESP to tell the installer to use it.

There is one stumbling stone though. Debian and Devuan and if I am not mistaken at least Ubuntu/Mint do add a generic directory into the ESP for their distributions. E.g. Stretch, Buster, Bullseye or Bookworm all add a directory called "debian". Older Devuan releases do the same. You see the problem?

If you want a dual boot for Chimaera and Daedalus you have to do some post processing, or only the later installation is bootable. The solution is to do another grub-install from the booted system with the option --bootloader-id=devuan4 as I am using it. Use efibootmgr to set the boot order as you like.

This rework is not to 100% update safe. I have been through grub updates that did re-establish the generic directory. So I had to redo my specific grub-install.

HTH,