Hi, I am the original reporter Andreas is talking about. I'm going to admit that I have no idea on how to use dbus activation. I only know how to start a service at boot via shell scripts. I understand if you won't support non-systemd init systems like sysvinit. I haven't maintained daemons, but from the looks of it, maintaining support for multiple inits is surely hard. However users who don't use systemd as their init, like Devuan users, Gentoo users, and Debian users who replaced systemd with sysvinit/openrc would appreciate it if upstream decided to support multiple inits. Gentoo users have a community which maintains their own iwd init script for openrc. Devuan users however, have to workaround this problem by converting the iwd systemd service file to a sysvinit script, and update-rc.d as root. If I haven't known about this, I would still be using wpa_supplicant by now. iwd actually made my wifi connection more reliable. When I was using wpa_supplicant, I had to reboot my system everytime the connection drops. With iwd, I only have to restart iwd and my connection is back. I figured that I should contribute back to the community by adding sysvinit support. So whatever decision you guys make, I will respect it. As you said, we can ship a modified version instead for non-systemd users. I am already preparing a fork of the iwd package for Devuan users[1]. The patch is ugly, but it works.