For such jobs I have a gparted life cd available to boot on usb. Write a new partition table, and then restart the Devuan installer and use manual partitioning.

And to get to another console while installing: use ALT-F2. There you can enter available commands. Back to installer with ALT-F1.

You might need to look for the uuid instead of the device. Check your fstab.

Short update: tried to install the weekly Bookworm into VBox for a check if Debian behaves the same, and failed. The iso is throwing machine checks and complains about the display. Will drill a bit deeper into that and update when I have results.

I am not really an expert on logging, I just use whats available every now and then.

Devuan uses its own package called rsyslog. There is also a doc package for this. Maybe that is a start for you. Somehow the stuff can be configured, and maybe yours is off for some reason.

To the raid: I have had my share of experiences with using Raid0 and later on trying Raid1/10 mainly on U320 SCSI, I would call it a disaster. Thats why I personally would walk away from any Raid if I have the choice of using SSDs instead. A single SSD never will cause the kind of hickups you can experience with Raids. A good backup always is required anyhow, and this is the lifesaver, not a Raid1.

And I think good SSDs are more reliable than any disk drive.

The logger creates a new file when the log reaches a specified size, and adds a number to the older log. e.g. syslog becomes syslog.1, the current contents remains in a new file syslog. if there was a syslog.1 before it becomes syslog.2. As many versions are kept as specified.

This function is called log-rotate.

Yes I didn't ... to little trouble recently ...

Don't worry, troubleshooting is adventure ...

Well, in summary, the required packages are present, the service is working as required. Still the same, when I try the date and time tool from the gnome-system-tools trying to go away from manual mode, the program is complaining about ntp not being present.

Thanks, I did not think about to use apt list to check if the program is coming directly under the same name. Just looked into the rcx.d directories.

And you can be sure I read the Beowulf release notes to find out about su -. I usually never use sudo, all my machines have a separate root account, and I have configured them with all tricks I have learned. I am an early adopter ...

Well, I haven't had any trouble yet with services not working, so I am blank in that aspect of the system. rc-status tells me the ntpsec service is running under the default level. And sysv-rc-conf lists an x for 2,3,4 and 5.

Well, just saw that the installation of sysv-rc-conf removed openrc. Well, reinstalled it and am being told to reboot immediately....

If non-free isn't pulled e.g. because of a typo or the repo being off you should get an error. apt update tells me:

# apt update
Holen:1 http://deb.devuan.org/merged daedalus InRelease [38,9 kB]
Ign:2 http://deb.devuan.org/merged daedalus/main amd64 Packages
Ign:3 http://deb.devuan.org/merged daedalus/main i386 Packages
Holen:4 http://deb.devuan.org/merged daedalus/contrib i386 Packages [47,3 kB]
Holen:5 http://deb.devuan.org/merged daedalus/contrib amd64 Packages [53,3 kB]
Holen:6 http://deb.devuan.org/merged daedalus/non-free amd64 Packages [117 kB]
Holen:7 http://deb.devuan.org/merged daedalus/non-free i386 Packages [90,5 kB]
Holen:2 http://deb.devuan.org/merged daedalus/main amd64 Packages [8.950 kB]

There just was a sync problem with the i386 main repo.

Check your sources.list thoroughly and show us what you are getting on apt update ...

Well, you are getting confused by mixing up two naming schemes.

1.) There is the Debian way to name their kernel/header packages: 6.0.0.6-amd64 tells you its the 6th version of the 6.0.0 kernel. This is a very Debian specific way to name the deb package.
2.) Linked to that is the official naming scheme by Linus: 6.0.12-1 corresponds to the 6.0.0.6 Debian package.

To avoid too much confusion, you might consider using dummy packages for kernel and header that make sure always the correct version is updated: linux-image-amd64 and linux-headers-amd64.

You might consider installing build-essentials or dkms, these packages also pull in the headers.

Still the same on the preview dated 2022-12-26.

The May version can be installed fine without mirror (the keyring update via network requires an user input thats not possible), and after first boot apt update does its job ok.

Why is this "1:" you call it epoch required? Well it works this way.

I scanned through the man apt_preferences, the Ubuntu wiki article, and other in the internet before posting here, didn't see that in the examples given ....