<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On Mon, 22 Dec 2014 21:30:38 -0500 Stefan Monnier
<a class="moz-txt-link-rfc2396E" href="mailto:monnier@iro.umontreal.ca"><monnier@iro.umontreal.ca></a> wrote:<br>
> >
<a class="moz-txt-link-freetext" href="http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562">http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562</a><br>
> <br>
> This points to line-number 562 in a long TODO list. Of course,
the item<br>
> at that line number is unrelated to this bug-report (tho I
presume it<br>
> was related back when this reply was sent).<br>
<br>
This is the original line:<br>
<pre><code>* There's currently no way to cancel fsck (used to be possible via C-c or c on the console)</code></pre>
Its line 659 now<br>
<br>
<a class="moz-txt-link-freetext" href="http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n659">http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n659</a><br>
<br>
<br>
> I think this is a very nasty regression that will hit
relatively few<br>
> people but will really piss them off.<br>
<br>
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. <br>
<br>
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<br>
<br>
> In my experience, systemd has introduced various different
*new* ways in<br>
> which the boot can get stuck in some long-running "operation"
(which<br>
> might just be waiting for a timeout). If we don't want to
alienate<br>
> users, we should raise the severity of this bug (and broaden
its scope).<br>
<br>
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.<br>
<br>
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<br>
<br>
"echo 'press ctrl - C to interrupt'; sleep 3;systemd-f*ck"<br>
<br>
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?<br>
<br>
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<br>
<br>
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<br>
<br>
Happy holidays<br>
</body>
</html>