Bug#758902: systemd: Please make ^C interrupt systemd-fsck

[alberto fuentes]

On Mon, 22 Dec 2014 21:30:38 -0500 Stefan Monnier
<monnier at iro.umontreal.ca> wrote:
> > 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).

This is the original line:

|* There's currently no way to cancel fsck (used to be possible via C-c or c on the console)|

Its line 659 now

http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n659


> I think this is a very nasty regression that will hit relatively few
> people but will really piss them off.

Not sure why you think they will be few people affected. I think almost
everybody is going to be hit by this at least once... probably more than
once. Computers have hard drives attached. They are checked at
semi-random intervals. If the hard drives is relatively large, it can
take from 20min to more than 1h to check.

I was biten by this once a month until one time I had to do a
presentation and the computer refused to bootup without checking the
disks, then decided to write the bug and disable checking on the disks
risking corruption
 
> 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).

While I agree and something generic and well implemented should be put
in place, i would be well off with a hack to interrupt it.

It would take less than 15 min to implement it to the systemd people to
avoid this 10+ years regresion. Calling a pre-script,or pre-service or
however systemd works

 "echo 'press ctrl - C to interrupt'; sleep 3;systemd-f*ck"

I dont know the details of how it would go in systemd but I dont think
this hack cant be put in place with the mighty systemd, can it?

The major problem is that the computer refuses to bootup without doing
the preventive check. Not even a reboot because you missed the ctrl - c
screen will help and you are forced to wait like is 1999

At the very least I would add 'patience is a virtue' or 'go outside and
play!' under the check. There is no reason not to joke about it :P

Happy holidays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141223/7db579cc/attachment-0002.html>