Some ideas: You determine your necessities. As long as you are happy with the OS and the software you are running, you may keep Beowulf.

The open question is: no more upgrades/safety fixes for Beowulf. Can you live with that? I have seen your posts about xorg security issues. They are getting fixed with Daedalus.

Risk with latest releases: removal of support for older hardware. Is a matter of test.

What bloat is concerned: yes its possible that things like CSD are trickling down. But they still can be removed. And an installation with --no-install-recommends may also help to keep the system clean from unwanted software.

Well, chaos. You have as well Testing as Unstable in your sources. What are you trying to achieve with this setup? Do you know what you are doing?

To clarify: Have you replaced the placeholder <user> with your username? And the placeholder <UUID> with the correct UUID of the device?

Maybe you show us with the drive connected:

# blkid
# lsblk

Then: the unallocated space is fine. But why does the ext4 file system have a msftdata flag, a Windows descriptor?

I maybe have an idea what went wrong:

You have prepared a bios_grub partition, why do you want to install grub to /? Use /dev/sda instead. If booted in legacy mode grub-install will take care for the rest.

This is true for Windows, where it is a must, but not for Linux.

In case of a GPT partitioned disk to be able to install/boot in Legacy mode you will need a grub_bios partition (1Mibyte, no file system, grub_bios flag set) to be able to save the parts of grub that goes in that area that is availabe on MBR partitioned disks and which is used by the GPT partitioning scheme in that case. I have done that successfully with Daedalus. Will only work for a pure Linux system.

The installation media must be booted in legacy mode to be able to install the legacy grub. May thats the problem?

Well, the Debian equivalent to Daedalus is Bookworm, not Trixie/Testing. A new installation of Daedalus would solve all issues.

The Daedalus DVD does allow to install Daedalus over Chimaera, its no upgrade. I am not aware of any easy way to use the DVD for the purpose of an upgrade. The DVD may be used as rescue system easily.

The upgraded Chimaera will be mostly like a newly installed Daedalus, except for specialities you may have installed and if you choose to keep the old configs. For sure you will have one or the other orphaned config or other remainders of older SW.
In some cases an upgrade will fail. The release notes usually give hints what to look for and what to pay attention to.

When the PC is online on the internet, an update is easily done via the console, I have done it already without issues. Prepare yourself by reading the available documentation:
https://files.devuan.org/devuan_daedalu … _notes.txt
https://www.devuan.org/os/documentation … o-daedalus
https://www.devuan.org/os/install

Most likely you haven't installed the meta packages linux-image-amd64 and linux-headers-amd64. They make sure kernel and headers are updated and consistent.

Also check if you have security enabled in your sources.list. Some read: https://www.devuan.org/os/packages

A patch is on its way through Debian repos ...

Your entry into the sources.list is wrong. You could use:

deb http://archive.devuan.org/merged ascii main

But I wouldn't fiddle and change the sources.list of my Daedalus for a single program.

Alternative: on the right hand top of the forum page is a link behind Packages to a search of the complete Devuan repo. Use that to search for leafpad. In the list of results then click on the ASCII package and you get another page with all available info about the latest version including a link to the file itself (look for Filename:). Click on the link and you get the deb downloaded. You can install it with dpkg -i or gdebi.

Normally deb.devuan.org should do the job alright. This is no real mirror but a round robin that should pick the next or fasted server available. If the picked out server has a problem then deb.devuan.org doesn't work.

But these issues should only be present temporarily.

In any case, I haven't seen any issue here in Germany with deb.devuan.org in the last days.