Abort/Retry/Fail
.... worked for many years.
Nobody to insert the original floppy? "Fail" is the only thing that
terminates. And "fail" invalidates all buffers, closes all files,
and leaves the missing floppy in an undefined state. However, the
kernel (and auto-mount) is ready to mount something else.
It is actually quite simple except for the problem that the
console (that gets the error messages), is not the remote terminal
used for STDERR_FILENO.
So, it seems that the file-system just needs another error-code that
can be interpreted by the application (like missing media??). Or you
can do what SunOs does, complains once, times out, then is ready
for another floppy to trash <grin>. The idea is to trash floppies,
not the OS.
I have a lap-top that came with Window$. I use it to run a board-level
debugger that has not been ported to Linux, and probably never will
be. I HATE it. However, it doesn't care if I misplaced the floppy
that had my open binaries on it.
We do need some such "don't-care" provisions for Linux. Certainly it's
possible without screwing up the good stuff we already have. I certainly
like the buffered floppy I/O. I don't like to wait for writes to
complete before I can do something else. This should not be changed.
All we need is some missing media exception handling that will allow
the "working-class" to misplace floppies.
Cheers,
Dick Johnson
Penguin : Linux version 2.3.36 on an i686 machine (400.59 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
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/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:24 EST