Package: systemd Version: 204-14 Followup-For: Bug #748056 Hello,
since this is a 'feature' I expect this is still present. I encountered this problem when one of my drive cables went loose and the drive became inaccessible. The drive was ad-hoc connected while placed physically outside of the computer case so this situation is forseeable but non-fatal with sysvinit. With systemd this renders the system non-bootable. There is no way to boot the system other than reconnecting the drive. I can understand that systemd does not want to automagically boot with some filesystem in fstab failing but it can at least offer the option when it stops the boot and requires user input anyway. The situation was further complicated by systemd not handling multiple consoles properly so the notices were printed and user input exected on disconnected serial console. Also candidate for big fat release note. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
