> http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562
This points to line-number 562 in a long TODO list. Of course, the item at that line number is unrelated to this bug-report (tho I presume it was related back when this reply was sent). I think this is a very nasty regression that will hit relatively few people but will really piss them off. But I don't think we should focus exclusively on fsck: C-c should be usable also to interrupt a "waiting for device to appear" or "waiting for the network to come up". So, basically, I think that any thingy which takes more than N second to complete should be interruptible via C-c (potentially with a prompt to confirm that the user really intended to interrupt this operation). In my experience, systemd has introduced various different *new* ways in which the boot can get stuck in some long-running "operation" (which might just be waiting for a timeout). If we don't want to alienate users, we should raise the severity of this bug (and broaden its scope). Stefan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org