Hi, On 05/09/2014 12:35, Svante Signell wrote: > Well, I've not been asked if I wanted to switch to systemd based boot > when upgrading. I think this is a bug in init system choice and should > be reported. How to go back to sysvinit?
Please ask on one of the support mailing lists (CC'ed). > Installed packages: > ii libpam-systemd:amd64 204-10 > ii libsystemd-daemon0:amd64 204-10 > ii libsystemd-id128-0:amd64 204-10 > ii libsystemd-journal0:amd64 204-10 > ii libsystemd-login0:amd64 204-10 > ii systemd 204-10 > ii systemd-sysv 204-10 > ii sysvinit 2.88dsf-53 > ii initscripts 2.88dsf-53 > ii sysv-rc 2.88dsf-53 > > Which ones can I safely remove when going back to sysvinit? You probably need to replace systemd-sysv with systemd-shim (to satisfy the dependency libpam-systemd) and install the package shipping /sbin/init instead (whatever it is called). Ansgar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/536cb764.1090...@debian.org
