Hi, the boot logs are found here... /var/log/boot (latest you need root access to read)

I agree with blackhole "If you're using the proprietary driver installation shell script from Nvidia's website, then rebuilding the kernel module for every kernel update is the norm."

Personally, I don't use dkms if at all possible, but I see it's usefulness with networked systems.

I also try to keep the kernel up to date, for me reinstalling the nVidia module is normal practice.

I noticed the nVidia .run packet from nVidia (as opposed to MIT) give the option to use dkms to rebuild the module and make it easier to reinstall the module when there is a change, you need the dkms package and underlying dependencies installed before you begin.

But as I said, for me it's normal to reinstall the nVidia module every time I upgrade to a new kernel, I usually check for updated nVidia during that time.

All the best.

cool!

I use nala as well, I think it works well, but there are times when I use the other package tools, but not snap or other app installers. DPKG and apt-get mostly. Nala has no reinstall switch... I like the colours. :-)

Here are some  notes on iwd install and configuration for svinit to open-rc script... sysd2v-0.3.sh

## The iwd.service is the systemd service for the iNet Wireless Daemon (iwd), a wireless management daemon developed by Intel for managing Wi-Fi connections on Linux systems.
##  It is designed to be a lightweight, efficient alternative to older tools like wpa_supplicant, offering minimal memory and CPU usage, built-in support for WPA/WPA2 and WPA3, and a command-line interface (iwctl) for managing wireless networks.
##  To use iwd, the service must be enabled and started using the commands sudo systemctl enable iwd.service and sudo systemctl start iwd.service.

## The service is controlled through the iwctl utility, which provides an interactive shell for managing wireless devices, scanning for networks, connecting to Wi-Fi, and viewing connection details.
##  For automatic network configuration, including DHCP and DNS resolution, iwd can be integrated with systemd-networkd or systemd-resolved, though additional configuration may be required for full functionality.
##  For example, if using resolvconf for DNS management, the iwd.service may need to be customized to include RuntimeDirectory=resolvconf and ReadWritePaths=/etc in its [Service] section to resolve permission issues with /run/resolvconf.

# apt install iwd -y
#
# sh /home/glenn/bin/sysd2v-0.3.sh /lib/systemd/system/iwd.service
# rsync -avh /home/glenn/local/other/backup/backup-etc-sys/etc/init.d/iwd.initd /etc/init.d/
# rsync -avh /home/glenn/local/other/backup/backup-etc-sys/etc/runlevels/iwd.initd /etc/runlevels/
# rsync -avh /home/glenn/local/other/backup/backup-etc-sys/etc/systemd/system/multi-user.target.wants/iwd.service /etc/systemd/system/multi-user.target.wants/
# chmod +x /lib/systemd/system/iwd.service
# chmod +x /etc/init.d/iwd.initd
# service iwd.initd start
# update-rc.d iwd.initd defaults

link to "You could try the sysd2v-0.3.sh conversion script, that might work:" http://www.trek.eu.org/devel/sysd2v/

I hope this helps

Welcome back! :-)

Hi, I have had the same problem with fail2ban with excalibur... (I've now decided to persist with this version of Devuan) Thank you for your efforts!

I didn't get any joy with the above examples or nixers script.

I eventuall tried to roll-back to fail2ban_1.0.2-2_all.deb.
python3-pyinotify was already installed.

When rollingback I got an error saying asynchat was not installed, so I installed python3-standard-asynchat_3.13.0-5_all.deb
and the fail2ban script started with out error.

I've only done one reboot since, so YMMV, but I hope it helps some of you here.
I'll see what happends when I eventually upgrade fail2ban later.
Cheers!

The file /etc/rc.conf maybe the file you need to set the config for cgroups.

A quick web search, (Brave-browser) gives all kinds, v1 & v2 as well as hybrid examples.

(I get an error in my boot logs about cpu and mem flags...)

I used the fstab line but my system stalls at startx, it does recover but I generally have given up before then... still learning.

there was a lot more info there...here's the top.

cgroup Mode
The primary setting is rc_cgroup_mode, which determines the cgroups version used:

rc_cgroup_mode="unified" – Uses cgroups v2 only (default in Alpine Linux since v3.19). 
rc_cgroup_mode="legacy" – Uses cgroups v1 only. 
rc_cgroup_mode="hybrid" – Uses both cgroups v1 and v2.
Note: To enable cgroups v2 exclusively, set rc_cgroup_mode="unified" in /etc/rc.conf and reboot for changes to take effect. 

Seems this is related more to openrc service manager. I hope this helps.

Hi, I've been seeing some quirky behaviour with opensnitch as well, but only that the gui with it's notifications did not start, I ended up setting it to start with plasma settings (I use KDE plasma, with xorg on Daedalus, again).

I had to leave excalibur because it lead to dep-hell.

I remember finding a python package for opensnitch and that helped my system a bit... ymmv

Happy new year to you all.

Great work, thank you for your efforts.

I realise I am surfing the rim here, but...

system service hwclock allows changes to or from system time.

Set the Hardware Clock to the current System Time.
# hwclock --systohc

Set the System Time from the Hardware Clock.
# hwclock --hctosys

# hwclock --set --date="8:20:05"

But, generally I set the bios to UTC and the system takes care of the rest.

All the best.

I often do this when tidying up the start process... for services I use and not everything available, especially for accessability services.

rc-update del sudo default
rc-update add sudo off
rc-update add ssh off
rc-update del ssh default
rc-update del saned default
rc-update add saned off
rc-update add nethack-common off
rc-update del nethack-common default
rc-update del fetchmail default
rc-update add fetchmail off
rc-update add exim4 off
rc-update del exim4 default

.... (plus a whole lot more where I profer to start them myself when required.)

If you type rc-update you'll get a complete list for your system. (I'm using open-rc)