apt update
apt list openssh-server
apt install openssh-server

Per default openssh-server listens on port 22. Always (after a reboot).

I am happy with my Devuan 6 Excalibur installations, both with Cinamon as desktop. Yes there are a few nicks and glitches, but nothing I would complain too much about. And what I have seen is inherited from Debian upstream.

I fear it doesn't work that way, never did.

Best for a Linux system: set the HW clock in the Bios to UTC. Set the time zone to your region.

Then install the packages ntpsec and ntpsec-ntpdate.

Last but not least: define a time server in /etc/ntpsec/ntp.conf. Works for me.

Note: when you dual boot with Windows, you have to change the registry to also set Windows to UTC.

I never used that kind of tools.

But one thing I know for sure: Truecrypt is no more maintained for now about 12 years or so. So I am not astonished that Veracrypt is a bit more comfortable.

It called crap by the users of kvm/qemu, VMware, Proxmox etc that only consider their tooling as approriate. Others complain about the license Oracle is using. Others don't like to use a Oracle product ..... I am happy to use it for 13 years now, beginning with my first Linux only PC.

Anyway, VBox was removed from Debian because of license (always was in contrib) and versioning problems, and I think they also lacked a maintainer. So its not available in the Devuan repos. Anyhow, no big problem, the Debian way of packaging was real crap in my eyes.

What I do for many years now: I pull a .deb fitting for the corresponding Debian release from https://www.virtualbox.org/wiki/Linux_Downloads, also load the extension pack suiting to the version, and install it with dpkg -i. Only two files required, the guest addition come within the .deb.

No I am not seing this error message.

First guess: make sure that the clock on your PC is set about correct.

Well, I was considering to write a bug report, but I did not do that because I am pretty sure it will be closed with the comment "works as specified".

Well, what I got from the debianforum.de, the rules in /etc/udev/rules.d have higher priority. Don't know if that is true.

My preference would be to leave the system directory /usr/lib/udev/rules.d alone and save my tweaks in /etc/udev/rules.d, clear distinction. That also was the suggestion from a very experienced person that looked at the problem and suggested the fix.

Yes it sucks. In the meantime I have a long document describing all these tweaks.

BTW: yes you have to create that edit unter /etc yourself. To make it work, either reboot or try a:

# udevadm control –reload
# udevadm trigger

Hi there, I guess the drive that isn't automounted is ext(x)-formatted, isn't it? Well, there is a new quirk in the udev rules from corporate actors inhibiting automount for ext(x)-partitions and others coming in with Trixie. Found that on the German Debian forum.

Check out for a file /usr/lib/udev/rules.d/64-ext4.rules, it reads:

# SPDX-License-Identifier: GPL-2.0-or-later
#
# Copyright (C) 2023 Oracle.  All rights reserved.
# Author: Darrick J. Wong <djwong@kernel.org>
#
# Don't let udisks automount ext4 filesystems without even asking a user.
# This doesn't eliminate filesystems as an attack surface; it only prevents
# evil maid attacks when all sessions are locked.
#
# According to http://storaged.org/doc/udisks2-api/latest/udisks.8.html,
# supplying UDISKS_AUTO=0 here changes the HintAuto property of the block
# device abstraction to mean "do not automatically start" (e.g. mount).
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ext2|ext3|ext4|ext4dev|jbd", ENV{UDISKS_AUTO}="0"

To override this rule you either change the "0" into a "1" with the risk that your change is overwritten from another update, or better write your own rule and save it to /etc/udev/rules.d/65-ext4.rules:

# extX-Dateisysteme automatisch mounten
SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="ext2|ext3|ext4|ext4dev|jbd", ENV{UDISKS_AUTO}="1" 

HTH

Ok, I am on conventional DSL here in Frankonia. No glas fibre yet directly to my home. They are working on that.

I use the standard Telekom DNS service and I at least currently have no issues with deb.devuan.org. And I have a Fritzbox bought on my own, no Speedport from Telekom any more.

Known problem, issues with DNS resolution by the internet providers. There are various threads here in the forum about this issue. They do not like the deb.devuan.org which is not a single IP but a so called round robin of various servers (used for load distribution). You can't do anything really. Only thing to try is to use a different DNS resolver.
And I would skip the "de" and just use http://deb.devuan.org/.....