Another day, another Devuan installation. Today I installed Daedalus with runit as the init system to get to grips with it.

To get an idea of how to manage services, I searched the Devuan websites/forums, but couldn't find much. So I had a look at the Artix and Void websites. Both have all the knowledge I was looking for, but they refer to subdirectories like

/etc/runit/sv/ and /run/runit/service/, which are not present under Devuan Daedalus.

This leads me to wonder what directories Daedalus uses for handling runit services and if there is any Devuan related documentation in regards of runit.

Scraping the filesystem brought up directories like:

- /etc/service
- /etc/runit/runsvdir

Hey everone,

today I've installed Devuan for the 1st time using the devuan_daedalus_5.0.1_amd64_netinstall.iso ISO. The only selected software to install was standard system utilities and for the init system I selected openrc. It's btw the first time ever using a non systemd OS.

After the initial installation I logged in as root to install some essential packages like sudo, git, curl and make. Next I've created a file in /etc/sudoers.d for my non-root-account.

Using the non-root-account I've installed all remaining packages including my prefered window manager, spectrwm, and rebooted. Finally I've created some entries in my crontab like:

*/15 * * * * /usr/bin/mw-mailsync

Sadly non of my cronjobs will take effect so I verified that the cron daemon is running via sudo rc-service cron status resulting in:

cron is running

And a pgrep cron results in:

2116

Following cron.log using sudo tail -f /var/log/cron.log confirms that my crontab entries will be executed:

2024-05-18T11:46:01.328023+02:00 hostname CRON[14006]: (my user) CMD (/usr/bin/mw-mailsync)

I'm certainly suffering from some kind of brain fart at the moment and don't see the obvious problem, which is why I'm turning to the swarm intelligence with confidence.

Thank you for your time and effort,
dexter