Chris Siebenmann
Ade Rixon
@thatcks No, you must be dreaming. Systemd saved us from that critical dependency.
It turns out that a whole lot of things explode when your system boots up with /bin/sh not working for some mysterious reason.
-
-
- View other replies
-
@aderixon The system actually booted all the way to a login prompt! I was really surprised. SysV init would have died immediately. -
@thatcks Is it worse to boot to an apparently working but hosed state, or fail early and obviously? - View other replies
-
@aderixon Init starts the early boot script that fsck's / and so on, script fails because /bin/sh is dead, rescue console fails ditto. Done. -
@thatcks Fair point. I guess in init case, you're booting an install image, whereas at least this way you can debug on the system itself. -
@aderixon Yeah. With SysV init the recovery is 'install image, or reboot and hope things work now' (which is what I wound up doing anyways).
-
-
Also, a Linux with systemd, sudo, and a (sudo-allowed) user with a non-/bin/sh shell can do a lot even when /bin/sh doesn't run.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.