lkml.org 
[lkml]   [1998]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: e2fsck...
On Fri, Nov 13, 1998 at 11:42:08AM -0500, Richard B. Johnson wrote:
> For the commands necessary to fix a disk, the fact that Ctrl-C doesn't
> work is of no consequence.

I utterly disagree.

1. You run badblocks and the disk makes a horrible noise, or it
spews out lots of numbers and you think it's causing more harm
than good.

You'd like ctrl-C to stop badblocks and get you back to the shell.

2. You run e2fsck, and it asks you some questions which you decide
are best answered with a debugfs session.

How do you quit e2fsck?

3. Your doing lots of kernel benchmarks, and you want to boot with
-b each time because that's fastest and most predictable.

Sometimes you want to quit a benchmark because you made a mistake,
edit a file, and carry on (or reboot and carry on).

Ctrl-C doesn't quit your scripts. It doesn't quit commands in
Emacs either, so if you foolishly do the wrong kind of string
substitution or a slow macro, you're stuck.

4. You're developing part of the kernel and it crashes a lot.
So you use -b to keep the reboot cycle short.

You type make -k. There are compile errors. Ctrl-C does nothing.

-- Jamie

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:0.045 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site