On Mon, Oct 6, 2014 at 2:17 PM, Michael Biebl <[email protected]> wrote: > Control: severity -1 normal > Am 06.10.2014 um 12:10 schrieb Roman Tsisyk: >>> From: Martin Pitt <[email protected]> >>> To: Roman Tsisyk <[email protected]>, [email protected] >>> Cc: >>> Date: Mon, 6 Oct 2014 11:30:35 +0200 >>> Subject: Re: Bug#764186: Can't remove systemd >>> Roman Tsisyk [2014-10-06 13:16 +0400]: >>>> systemd is the active init system, please switch to another before >>>> removing systemd. >>> >>> This quite clearly explains why the removal rightly fails, and this is >>> a good thing -- otherwise you would end up with an unbootable system. >>> You can install sysvinit-core or upstart first in order to switch. >> >> I have sysvinit-core installed, but I still can't remove systemd: > > You need to reboot to make sysvinit the active init.
I have absolutely no guarantee that my system will boot up properly after that. It is uncommon to force reboot after installing/remove software. Is it possible to select init system using update-alternatives or something like that? Thanks! -- WBR, Roman Tsisyk <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
