[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 Architecture Description +++-====================-===============-===============-============================================== ii sysvinit-core 2.88dsf-53.2 i386 System-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
