Yeah, but they're still handy from time to time. It's certainly quicker to
pop a disk in and type "mdir", than to put it in, type "mount /floppy; ls
/floppy; umount /floppy" or similar. You get the picture. Not that you
don't have a valid point, too.
> That said, I have a few other thoughts. First, can't the kernel
> detect when a new floppy is inserted? I can't remember if there is an
> interupt generated when the floppy seats or not.
If I'm not mistaken, and I think has already been mentioned somewhere before
in this thread, these interrupts where determined to be unreliable under some
circumstances. Anybody remember the details?
> And second, can't you just avoid the whole issue by keeping the floppy
> accessed at all time while you use it? Something like:
> sleep 3600 </dev/fd0 &
> or some such to lock the pages after they are read?
That's basically what I'd propose "mopen" do... Hold it open 'til the user
does a "mclose". Of course, if you yank the disk out in the middle, all bets
are off.
-Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/