Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Package: sysvinit-core Version: 2.88dsf-53.2 Severity: critical After a failed switch to systemd today (Debian bug #751585), I tried to switch back to sysvinit but found /sbin/init missing after a reboot, which of course prevented the system from booting. /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. I've attached dpkg and apt logfiles, starting with the systemd installation. Note that systemd printed systemd is the active init system, please switch to another before removing systemd when I tried to remove it; but it gave no guidance on how to do this. Did this mean to install sysvinit and reboot (which is what I did)? Was I supposed to do something with update-alternatives or similar, or was I actually supposed to be running sysvinit somehow before rebooting? It's possible this is actually a bug in dpkg, apt, or systemd. - Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysvinit-core depends on: ii debconf [debconf-2.0] 1.5.53 ii debianutils4.4 ii initscripts2.88dsf-53 ii libc6 2.19-1 ii libselinux12.3-1 ii libsepol1 2.3-1 ii sysv-rc2.88dsf-53 ii sysvinit-utils 2.88dsf-53 sysvinit-core recommends no packages. sysvinit-core suggests no packages. -- debconf information: sysvinit/hurd-fix-inittab: 2014-06-14 08:58:14 startup archives unpack 2014-06-14 08:58:15 install systemd:amd64 none 204-10 2014-06-14 08:58:15 status half-installed systemd:amd64 204-10 2014-06-14 08:58:15 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:15 status half-installed systemd:amd64 204-10 2014-06-14 08:58:15 status triggers-pending man-db:amd64 2.6.7.1-1 2014-06-14 08:58:16 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:16 status unpacked systemd:amd64 204-10 2014-06-14 08:58:16 status unpacked systemd:amd64 204-10 2014-06-14 08:58:16 trigproc dbus:amd64 1.8.2-1 1.8.2-1 2014-06-14 08:58:16 status half-configured dbus:amd64 1.8.2-1 2014-06-14 08:58:17 status installed dbus:amd64 1.8.2-1 2014-06-14 08:58:17 trigproc man-db:amd64 2.6.7.1-1 2.6.7.1-1 2014-06-14 08:58:17 status half-configured man-db:amd64 2.6.7.1-1 2014-06-14 08:58:20 status installed man-db:amd64 2.6.7.1-1 2014-06-14 08:58:21 startup packages configure 2014-06-14 08:58:21 configure systemd:amd64 204-10 none 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status triggers-pending dbus:amd64 1.8.2-1 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:21 status unpacked systemd:amd64 204-10 2014-06-14 08:58:22 status half-configured systemd:amd64 204-10 2014-06-14 08:58:22 status triggers-awaited systemd:amd64 204-10 2014-06-14 08:58:22 trigproc dbus:amd64 1.8.2-1 none 2014-06-14 08:58:22 status half-configured dbus:amd64 1.8.2-1 2014-06-14 08:58:22 status installed systemd:amd64 204-10 2014-06-14 08:58:22 status installed dbus:amd64 1.8.2-1 2014-06-14 08:58:22 startup packages remove 2014-06-14 08:58:22 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:22 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23 status installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 08:58:23
Bug#751589: [Pkg-sysvinit-devel] Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
[Michael Gold] /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. This is quite strange. My version 2.88dsf-53.2 of sysvinit-core in unstable contain these files: root@freedomboxtest:~# dpkg -l sysvinit-core Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++--===-===-== ii sysvinit-core2.88dsf-53.2i386System-V-like init utilities root@freedomboxtest:~# dpkg -L sysvinit-core|grep sbin /sbin /sbin/init /sbin/halt /sbin/runlevel /sbin/shutdown /sbin/poweroff /sbin/reboot /sbin/telinit root@freedomboxtest:~# Is the amd64 build broken? Or did dpkg mess up something? I switched from systemd to sysvinit earlier today in a test machine using unstable, so that should work fine too. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Control: reassign -1 systemd-sysv 204-6 On 2014-06-14 16:18 +0200, Michael Gold wrote: Package: sysvinit-core Version: 2.88dsf-53.2 Severity: critical After a failed switch to systemd today (Debian bug #751585), I tried to switch back to sysvinit but found /sbin/init missing after a reboot, which of course prevented the system from booting. /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. I've attached dpkg and apt logfiles, starting with the systemd installation. Those show that sysvinit-core was unpacked with systemd-sysv still in place which is bad because systemd-sysv Replaces sysvinit-core. The systemd-sysv package should declare a Conflicts rather than Breaks on sysvinit-core to prevent this from happening. Note that systemd printed systemd is the active init system, please switch to another before removing systemd when I tried to remove it; but it gave no guidance on how to do this. Did this mean to install sysvinit and reboot (which is what I did)? Yes, you first install sysvinit-core, removing systemd-sysv in the process. After you rebooted, you may remove systemd if you so desire. These are the relevant lines from dpkg.log which show that sysvinit-core was unpacked with systemd-sysv still in place. 2014-06-14 09:09:16 install sysvinit-core:amd64 2.88dsf-53 2.88dsf-53.2 2014-06-14 09:09:16 status half-installed sysvinit-core:amd64 2.88dsf-53 2014-06-14 09:09:17 status unpacked sysvinit-core:amd64 2.88dsf-53.2 2014-06-14 09:09:35 status installed systemd-sysv:amd64 204-10 2014-06-14 09:09:36 remove systemd-sysv:amd64 204-10 none 2014-06-14 09:09:36 status half-configured systemd-sysv:amd64 204-10 2014-06-14 09:09:36 status half-installed systemd-sysv:amd64 204-10 2014-06-14 09:09:36 status triggers-pending man-db:amd64 2.6.7.1-1 2014-06-14 09:09:37 status config-files systemd-sysv:amd64 204-10 2014-06-14 09:09:37 status not-installed systemd-sysv:amd64 none 2014-06-14 09:09:38 configure sysvinit-core:amd64 2.88dsf-53.2 none 2014-06-14 09:09:38 status unpacked sysvinit-core:amd64 2.88dsf-53.2 2014-06-14 09:09:39 status half-configured sysvinit-core:amd64 2.88dsf-53.2 2014-06-14 09:09:39 status installed sysvinit-core:amd64 2.88dsf-53.2 Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Control: reopen -1 Closing bugs which render the system unbootable seems a bit premature to me. On 2014-06-14 17:03 +0200, Michael Biebl wrote: Am 14.06.2014 16:55, schrieb Sven Joachim: Control: reassign -1 systemd-sysv 204-6 On 2014-06-14 16:18 +0200, Michael Gold wrote: Package: sysvinit-core Version: 2.88dsf-53.2 Severity: critical After a failed switch to systemd today (Debian bug #751585), I tried to switch back to sysvinit but found /sbin/init missing after a reboot, which of course prevented the system from booting. /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. I've attached dpkg and apt logfiles, starting with the systemd installation. Those show that sysvinit-core was unpacked with systemd-sysv still in place which is bad because systemd-sysv Replaces sysvinit-core. The systemd-sysv package should declare a Conflicts rather than Breaks on sysvinit-core to prevent this from happening. This is not going to happen as this conflicts with #748355. #748355 is about the conflict with sysvinit, not with sysvinit-core. We are actually going to drop the Breaks. Okay, then sysvinit-core must declare the necessary Conflicts: systemd-sysv. Feel free to reassign back. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751589: [Pkg-sysvinit-devel] Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
On Sat, Jun 14, 2014 at 16:47:45 +0200, Petter Reinholdtsen wrote: [Michael Gold] /sbin was available in the emergency shell and contained some files, but 'init' wasn't there. 'dpkg -L sysvinit-core' ended at the line '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.). I eventually figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and then I was able to boot the system normally. This is quite strange. My version 2.88dsf-53.2 of sysvinit-core in unstable contain these files: ... root@freedomboxtest:~# dpkg -L sysvinit-core|grep sbin /sbin /sbin/init /sbin/halt /sbin/runlevel /sbin/shutdown /sbin/poweroff /sbin/reboot /sbin/telinit root@freedomboxtest:~# Is the amd64 build broken? Or did dpkg mess up something? I switched from systemd to sysvinit earlier today in a test machine using unstable, so that should work fine too. The build is fine--those files are there in 2.88dsf-53 and 2.88dsf-53.2, and dpkg -L sysvinit-core shows them now. And after all, /sbin/init appeared after running dpkg -i on the same file apt tried to install. But I'm certain they were missing and the output ended at /sbin when I ran the command in the emergency shell. It seemed strange that the /sbin directory would be included without any files in it. I was also surprised to see the manual, init.8.gz, without the associated binary. -- Michael signature.asc Description: Digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Am 14.06.2014 17:15, schrieb Sven Joachim: This is not going to happen as this conflicts with #748355. #748355 is about the conflict with sysvinit, not with sysvinit-core. Fair enough. Using Conflicts: sysvinit-core in systemd-sysv would have been the correct thing to do anyway, i.e. the fix for #733240 was not entirely correct. That said, I can not reproduce the sequence of events which make /sbin/init dissappear. I've installed systemd-sysv in a VM, then ran apt-get install sysvinit-core and /sbin/init was available afterwards. So something else must have happened -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
On Sat, Jun 14, 2014 at 17:34:21 +0200, Michael Biebl wrote: That said, I can not reproduce the sequence of events which make /sbin/init dissappear. I've installed systemd-sysv in a VM, then ran apt-get install sysvinit-core and /sbin/init was available afterwards. So something else must have happened Did you try apt-get remove systemd? According to apt-history that was the first command I ran after installing it. -- Michael signature.asc Description: Digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
tags 751589 + unreproducible thanks Am 14.06.2014 18:22, schrieb Michael Gold: On Sat, Jun 14, 2014 at 17:34:21 +0200, Michael Biebl wrote: That said, I can not reproduce the sequence of events which make /sbin/init dissappear. I've installed systemd-sysv in a VM, then ran apt-get install sysvinit-core and /sbin/init was available afterwards. So something else must have happened Did you try apt-get remove systemd? According to apt-history that was the first command I ran after installing it. You can't remove the systemd package while systemd is still the active init. How did you force the removal? That said, even with that sequence of events /sbin/init is available here. I'm marking the bug as unreproducible until we have steps how we can reproduce the issue. root@pluto:/# apt-get remove systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: sysvinit-core The following packages will be REMOVED: systemd systemd-sysv The following NEW packages will be installed: sysvinit-core 0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded. Need to get 0 B/130 kB of archives. After this operation, 4909 kB disk space will be freed. Do you want to continue? [Y/n] debconf: delaying package configuration, since apt-utils is not installed dpkg: systemd-sysv: dependency problems, but removing anyway as you requested: sysvinit depends on sysvinit-core | upstart | systemd-sysv; however: Package sysvinit-core is not installed. Package upstart is not installed. Package systemd-sysv is to be removed. (Reading database ... 13159 files and directories currently installed.) Removing systemd-sysv (204-10) ... Selecting previously unselected package sysvinit-core. (Reading database ... 13142 files and directories currently installed.) Preparing to unpack .../sysvinit-core_2.88dsf-53.2_amd64.deb ... Unpacking sysvinit-core (2.88dsf-53.2) ... Setting up sysvinit-core (2.88dsf-53.2) ... Not restarting sysvinit (Reading database ... 13167 files and directories currently installed.) Removing systemd (204-10) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--remove): subprocess installed pre-removal script returned error exit status 1 Running in chroot, ignoring request. Running in chroot, ignoring request. Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@pluto:/# ls /sbin/init -la -rwxr-xr-x 1 root root 40552 Jun 7 23:32 /sbin/init root@pluto:/# dpkg -S /sbin/init sysvinit-core: /sbin/init -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
[Hit the send button a bit too early] Am 14.06.2014 19:34, schrieb Michael Biebl: As I'm not able to reproduce the issue, I'm unable to test if replacing Breaks with Conflicts actually fixes this particular bug you are seeing. Michael, could you test if you can reliably reproduce the issue? If so, I can provide you with updated systemd package where Breaks is replaced with Conflicts and I'd like you to also test with those packages. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Am 14.06.2014 18:31, schrieb Michael Biebl: That said, even with that sequence of events /sbin/init is available here. I'm marking the bug as unreproducible until we have steps how we can reproduce the issue. root@pluto:/# apt-get remove systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: sysvinit-core The following packages will be REMOVED: systemd systemd-sysv The following NEW packages will be installed: sysvinit-core 0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded. Need to get 0 B/130 kB of archives. After this operation, 4909 kB disk space will be freed. Do you want to continue? [Y/n] debconf: delaying package configuration, since apt-utils is not installed dpkg: systemd-sysv: dependency problems, but removing anyway as you requested: sysvinit depends on sysvinit-core | upstart | systemd-sysv; however: Package sysvinit-core is not installed. Package upstart is not installed. Package systemd-sysv is to be removed. (Reading database ... 13159 files and directories currently installed.) Removing systemd-sysv (204-10) ... Selecting previously unselected package sysvinit-core. (Reading database ... 13142 files and directories currently installed.) Preparing to unpack .../sysvinit-core_2.88dsf-53.2_amd64.deb ... Unpacking sysvinit-core (2.88dsf-53.2) ... Setting up sysvinit-core (2.88dsf-53.2) ... Not restarting sysvinit (Reading database ... 13167 files and directories currently installed.) Removing systemd (204-10) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--remove): subprocess installed pre-removal script returned error exit status 1 Running in chroot, ignoring request. Running in chroot, ignoring request. Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@pluto:/# ls /sbin/init -la -rwxr-xr-x 1 root root 40552 Jun 7 23:32 /sbin/init root@pluto:/# dpkg -S /sbin/init sysvinit-core: /sbin/init As I'm not able to reproduce the issue, I'm unable to test if replacing Breaks with Conflicts actually fixes this particular bug you are seeing. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
On 2014-06-14 19:37 +0200, Michael Biebl wrote: [Hit the send button a bit too early] Am 14.06.2014 19:34, schrieb Michael Biebl: As I'm not able to reproduce the issue, I'm unable to test if replacing Breaks with Conflicts actually fixes this particular bug you are seeing. Michael, could you test if you can reliably reproduce the issue? I could reproduce it by manually downgrading sysvinit to an older version and then removing systemd (this is the situation Michael was in). In this case, apt-get decides to upgrade sysvinit and unpacks sysvinit-core before removing systemd-sysv: , | # apt-get remove systemd | Reading package lists... Done | Building dependency tree | Reading state information... Done | The following extra packages will be installed: | sysvinit sysvinit-core | The following packages will be REMOVED: | systemd systemd-sysv | The following NEW packages will be installed: | sysvinit-core | The following packages will be upgraded: | sysvinit | 1 upgraded, 1 newly installed, 2 to remove and 0 not upgraded. | Need to get 0 B/211 kB of archives. | After this operation, 5042 kB disk space will be freed. | Do you want to continue? [Y/n] | Preconfiguring packages ... | Selecting previously unselected package sysvinit-core. | (Reading database ... 13913 files and directories currently installed.) | Preparing to unpack .../sysvinit-core_2.88dsf-53.2_i386.deb ... | Unpacking sysvinit-core (2.88dsf-53.2) ... | Replaced by files in installed package systemd-sysv (204-10) ... | Processing triggers for man-db (2.6.7.1-1) ... | dpkg: dependency problems prevent configuration of sysvinit-core: | systemd-sysv (204-10) breaks sysvinit-core and is installed. | | dpkg: error processing package sysvinit-core (--configure): | dependency problems - leaving unconfigured | Errors were encountered while processing: | sysvinit-core | E: Sub-process /usr/bin/dpkg returned an error code (1) ` A subsequent apt-get remove systemd systemd-sysv then leaves the system without /sbin/init. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751589: [Pkg-sysvinit-devel] Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
Control: tags -1 - unreproducible Control: reassign -1 sysvinit-core systemd-sysv Control: found -1 sysvinit/2.88dsf-53 Control: found -1 systemd/204-6 You can't remove the systemd package while systemd is still the active init. How did you force the removal? That said, even with that sequence of events /sbin/init is available here. I'm marking the bug as unreproducible until we have steps how we can reproduce the issue. apt-get install sysvinit-core apt-get install systemd-sysv apt-get remove systemd-sysv dpkg --configure -a This bug shows an embarrassing lack of mastery of dpkg package relationship semantics on the part of those managing the systemd packaging. You currently have: Replaces: sysvinit ( 2.88dsf-44~), sysvinit-core Breaks: sysvinit-core Policy 7.3 is quite clear on this: Normally a `Breaks' entry will have an earlier than version clause; such a `Breaks' is introduced in the version of an (implicit or explicit) dependency which violates an assumption or reveals a bug in earlier versions of the broken package, or which takes over a file from earlier versions of the package named in `Breaks'. This use of `Breaks' will inform higher-level package management tools that the broken package must be upgraded before the new one. If your package relationship does not involve an earlier than clause, it should be a Conflicts, *not* a Breaks. It was certainly an oversight on my part that the sysvinit-core package didn't declare a Conflicts on systemd-sysv and upstart; but to actively declare a Breaks for something that every Debian Developer should know requires a Conflicts is something else. I have committed the fix for this to sysvinit git: Package: sysvinit-core Conflicts: systemd-sysv, upstart Replaces: sysvinit ( 2.88dsf-44~), systemd-sysv, upstart and I will upload it just as soon as I untangle the current status of sysvinit vis-a-vis unstable vs. experimental. Please make the corresponding fix on the systemd side. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit
On Sat, Jun 14, 2014 at 18:31:25 +0200, Michael Biebl wrote: Did you try apt-get remove systemd? According to apt-history that was the first command I ran after installing it. You can't remove the systemd package while systemd is still the active init. How did you force the removal? I just ran the apt-get commands shown in the apt-history.log, without any flags to force it, and didn't run any dpkg commands (except the eventual dpkg -i to recover). I think what Sven reproduced is what happened to me. According to the logs, I started with sysvinit-core 2.88dsf-53 (not 53.2). Note that the systemd removal didn't actually work until 9:22, when I was running sysvinit again. But one of the earlier commands left me without an init. -- Michael signature.asc Description: Digital signature
