Hi Matthew! > I ran `apt install runit-init` and then attempted to reboot with > `/sbin/reboot`, `/sbin/poweroff`, `init 0` & `init 6`, all to no > effect; no error messages were returned and the exit status of all of > the commands was zero.
This happens because the computer is still running systemd as the init process and any runit commands will therefore not work until the computer has been rebooted with runit as the init system. I also don't think there is a trivial way to solve this problem. And, after all, with systemd being the default and supported init system on Debian as per GR decision, you are on your own anyways when you decided to switch to one of the alternative init systems. And since runit is not officially supported to be the init system in Debian, I don't think this bug qualifies as release critical either. I'd be tempted to lower the severity to 'normal'. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
