If debian systemd version 44 is re-installed over systemd-196, here is a summary of what to do to clean-up afterwards. Did I miss anything?
First, back-up your config files in /etc/systemd, because "make install" will over-write them. Then, from the systemd-196 build directory, sudo make install "comment-out" the line with non-existent group "lock" or create this group, sudo vim /usr/lib/tmpfiles.d/legacy.conf or sudo groupadd -r lock Creating this group avoids having to remember to edit "legacy.conf". sudo ln -sf /usr/lib/systemd/systemd /bin/systemd sudo ln -sf /usr/lib/systemd/systemd /sbin/init sudo ln -sf /usr/bin/systemctl /bin/systemctl sudo rm /bin/systemctl /bin/systemd-ask-password /bin/systemd-journalctl /bin/systemd-loginctl /bin/systemd-machine-id-setup /bin/systemd-notify /bin/systemd-tmpfiles /bin/systemd-tty-ask-password-agent cd /usr/lib/systemd sudo rm debian-fixup systemd-detect-virt systemd-readahead-collect systemd-readahead-replay systemd-remount-api-vfs systemd-uaccess sudo rm system/sys-kernel-security.mount system/sysinit.target.wants/sys-kernel-security.mount system/debian-fixup.service system/systemd-remount-api-vfs.service system/local-fs.target.wants/systemd-remount-api-vfs.service system/sysinit.target.wants/debian-fixup.service If you are using "--bindir=/bin" with "configure", cd /usr/bin sudo rm systemd-analyze systemd-cat systemd-cgls systemd-cgtop systemd-nspawn systemd-stdio-bridge Make sure custom "unit" files in /etc/systemd/system have not been overwritten. Restart systemd-196 sudo systemctl daemon-reload Continue with upgrades, if they failed with systemd-44 systemd. And, here is a service file for named/bind9 which you can try installing into /etc/systemd/system, modified from http://lists.fedoraproject.org/pipermail/devel/2012-November/173500.html: [Unit] Description=Domain Name Server After=network-manager.service [Service] Type=forking ExecStart=/usr/sbin/named -u bind ExecReload=/bin/kill -HUP $MAINPID ExecStop=/bin/kill -TERM $MAINPID PrivateTmp=true TimeoutSec=45 Restart=always RestartSec=1 [Install] WantedBy=multi-user.target Alternatively, modify the /etc/init.d/bind9 LSB header. There is # Should-Start: $network $syslog instead of # Required-Start: <...> $network but still, that is not enough to sequence "named" and "network-manager". Instead, use explicitly # Required-Start: <...> network-manager and then "named" will start after "network-manager" and stop spewing gratuitous "network unreachable" errors - assuming that you are using Network-Manager for networking. James -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
