I found some debian packages in daedalus-backports.  But warning... by default it does try to pull in systemd-standalone-sysusers, and I would strongly urge you to pin this out so that it will not get installed.  There is a non-systemd package called opensysusers which will install in its place if the systemd* packages are pinned from getting installed.

For example, this is my apt pin in /etc/apt/preferences.d/00nosystemd:

Make sure the daedalus-backports repo is active in sources.list.

# apt policy incus

# apt install -t daedalus-backports incus

I have not installed, nor do I know if these packages will work.  I see that systemd is a "suggested" package, but not a dependency.  Let us know how it goes.  Thanks.

Edit:  grammar and spelling.

Sorry for taking so long for reporting back, but this took a while. 

I did a physical install on a 13 year old dell server.  I made no changes at all, except for a user account name change and password change during installation.  I simply installed and tested.  My testing was centered on simply booting up, logging in, and rebooting into the next init. 

After installing all inits (boot options) worked fine, except s6-66.  My partition scheme is:

sda is a msdos master boot record, not gpt.
/  is /sda1
/home is /sda2
swap is /sda3
/mnt/data1 is sdb1

The first boot into s6-66, I got the same ModemManager error as reported above:

The system was not in a usable state so I was not able to view the log files, either locally or with ssh.  The second boot attempt I did not see that error and I got to the lightdm login screen.  The regular user was not able to login.  A login attempt with the correct user/pass just refreshed the page.  However, the root user was able to login.  Further checking:

ls -a /home

 
showed the entire /home folder as empty.  The /home partition did not get mounted at boot.  A manual mount of /home did work and then I was able to login.  I searched the log files and I found no mention about a mount error.  My fstab is:

I did notice that the s6-66 reversed the partitions sda -> sdb, sdb -> sda.  This was as far as I got with s6-66 as the third and 4th boot attempts produced the same modemmanager error. 

So, to recap, the s6-66 method did not mount the /home partition correctly at boot on the couple of times that it did work correctly.

If you can tell me what to check I will be glad to test further.  But without an error notation in a log file, I don't know where to start and I am very unfamiliar with inits.  I am not a very good tester, but I did have some time to test.

Testing was done from within virtualbox after installing, not a physical install on a hard drive, using a devuan host system - ceres (unstable)

At boot:

grub default selection - It worked fine the first boot, and maybe the second, and then it didn't.  When it did not successfully boot -

I logged in as root and  ran

"service lightdm start" will start the X session (lightdm) from the physical console of the virtual machine.  I successfully started Xfce by logging in as the user and entering "startxfce4".  I made some text bold to make it stand out, as it raised some questions with me.

While it was not successfully booted into X, I ssh(ed) into the machine and got this information:
/home/user/.xsession-errors

/var/log/lightdm/seat0-greeter.log
# cat /var/log/lightdm/seat0-greeter.log

/var/log/syslog
noting mentioned, warnings or errors regarding xorg or lightdm

Just to document what package if any had systemd mentioned -
root@init-diversity:/home/craig# dpkg -l | grep systemd
ii  dhcpcd   1:9.4.1-24~deb12u3     all  DHCPv4 and DHCPv6 dual-stack client (init.d script and systemd unit)

So, sometimes it works, sometimes it does not and I can't report what is wrong.  I thought the default selection was sysvinit, but the sysvinit selection works fine.  I have not checked the grub entries for any difference between the two selections.

grub sysvinit selection - it worked fine.
grub s6-rc selection - it worked fine.

grub s6-66 selection - fails to boot.
boot hangs with the message on screen that:

A virtualbox driver issue perhaps?  Repeated attempts with this method does the same thing with the same message.

grub runit selection - it worked fine.
This was my first time using runit and was very impressed with its speed and smoothness.

grub openrc selection - fails to boot.
I get the same or similar error messages as using sysvinit.
/home/user/.xsession-errors

cat /var/log/lightdm/seat0-greeter.log
(entire log, nothing excluded)

On the physical VM screen, it hangs at:

This or whatever it is trying to load next, but is not displayed yet, may be the problem.

My changes to the default installed system:
Removed vim and firmware-libertas firmware-myricom firmware-netxen firmware-qlogic ti-connectivity firmware-atheros firmware-bnx2x firmware-brcm80211
Installed gtkhash thunar-gtkhash libb2-1 geany autofs

I will be glad to assist in troubleshooting.  Please let me know.  This is an easy to use way to test and experiment with multiple init systems within the same install.  This is a very interesting concept.

Edit:  corrected typing mistakes.

This page shows what the sources.list should look like in daedalus, and this is only showing the main repo. 
https://www.devuan.org/os/documentation … o-daedalus

You may want to add the additional options like adding "contrib non-free non-free-firmware" to each line.

But at any rate it should still show up as it is there with "main".   

Have you run "apt update" before looking for it? Or, are you using synaptic?  A better question is, how are you trying to look for it and install it, with a terminal using "apt" or with the gui program synaptic?  If using apt you must might first want to run "apt update", and if using synaptic, click on "Reload" first, before searching.

Hope this helps.

Just in case someone is interested, this link helped me out recently.  I had a Peppermint Devuan install and found it easier to just remove the dmo packages and revert to an all devuan install - including their multimedia packages.  I noticed no difference with no breakage.  Upgrades were easier too.

How to remove dmo packages - deb.multimedia
https://forums.linuxmint.com/viewtopic.php?t=227270

I ran into this problem yesterday while trying to do an upgrade of a ceres install.  This is my daily driver so it gets updated almost daily.  Therefore it was current to within a one to two day period.  When trying to do an apt upgrade I get this:

If I try to do an apt dist-upgrade, I get this:

There are no held packages.  The command "apt-mark showhold" produces no output, and there are no locked packages in synaptic as I do not use synaptic in ceres.

I know there was a lot of work done in the past to eliminate libsystemd0 from our system and I wonder if something new is trying to pull it back in?

Edit: added the held package information.

Thank you ffp!  This got pipewire working on a daedalus install that has been dist-upgraded from ascii > beowulf > chimaera > to daedalus!

I was wondering the same thing, but delgado posted before I did.

This WSL is good for a some people, but I only need windows to run my tax program once or twice a year, and a couple other programs during the year.  I prefer to use a windows virtual machine in a devuan host system than to use WSL in a windows machine.  But this was fun to play with.

From the link above,

or "<your-name>" for the script.  Make it executable.

Change this line in the script, or keep it as is:

- or -

Follow the instructions on adding the symlinks.  Then try to use the usual service commands to start/stop/status:
service <your-name> start/stop/status

Put your wireguard profile file in /etc/wireguard .  Give it your preferred name, maybe "wg0" or <your-name>.  The name you give it should be the same through the sysvinit script, and the profile name, I think.

Does openrc use sysvinit scripts?  I am not too familiar with openrc/runit/s6, yet, so if I am totally incorrect, please forgive me.

I used this info to create a sysvinit start script using my own wireguard profile config.  I hope it helps.

https://www.procustodibus.com/blog/2021 … it-script/

Maybe not yet.
But it has been added to the testing/ceres repo.

I apologize even before I ask this as I hope that I do not appear to be impatient, but will php packages for daedalus be built by tdrnetworks.com any time soon?  Just trying to plan an upgrade eventually.  I have used these packages without issue for over 3 years now, so I trust them.

I did run a test by upgrading to deb.sury.org's packages for daedalus and they appear to work fine, so this is a possibility.  If using sury.org's repo one will need to install "systemd-standalone-tmpfiles" beforehand. 

But I did get an awful feeling when I willfully installed something with "systemd" in its name.