> linked units from /etc/systemd/system are still being read. This needs a bigger hammer.
Fixed in git.
> reboot is hanging
This was due to /lib/lsb/init-functions.d/40-systemd which diverted SysV init scripts to systemctl which then ignored those as we want to disable SysV support for deputy systemd. Fixed in git.
> I haven't tested dist-upgrade to 16.04 yet.
Done now. It mostly works except for a two-minute hang in grub-common.postinst when trying to start grub-common.service. This gets into a deadlock due to the LSB hook reappearing while the deputy systemd is still running, and after the timeout grub-common is in a failed state. What works is to manually do "sudo initctl stop systemd; sudo rm -r /run/systemd/system; sudo apt-get -f install". After the dist-upgrade you need to run "sudo reboot -f".
Status update:
> linked units from /etc/systemd/system are still being read. This needs a bigger hammer.
Fixed in git.
> reboot is hanging
This was due to /lib/lsb/ init-functions. d/40-systemd which diverted SysV init scripts to systemctl which then ignored those as we want to disable SysV support for deputy systemd. Fixed in git.
> I haven't tested dist-upgrade to 16.04 yet.
Done now. It mostly works except for a two-minute hang in grub-common. postinst when trying to start grub-common. service. This gets into a deadlock due to the LSB hook reappearing while the deputy systemd is still running, and after the timeout grub-common is in a failed state. What works is to manually do "sudo initctl stop systemd; sudo rm -r /run/systemd/ system; sudo apt-get -f install". After the dist-upgrade you need to run "sudo reboot -f".
I updated https:/ /launchpad. net/~pitti/ +archive/ ubuntu/ systemd to systemd 204-5ubuntu20. 19pitti3 with the recent fixes, and this should now work reasonably well except for upgrades. Please test with snapd!