Mail Archives: opendos/1997/02/15/00:17:18
On Fri, 14 Feb 1997, yeep wrote:
> > for it before doing anything else. What? In a multitasking OS?
> > Heck, any commands that don't give me my prompt back get shoved
> > in the background, so that copy command becomes:
> >
> > $cp txt/* /a/ &
> >
> > And the prompt is back.
>
> Yes, but in the text above I said that in Linux (or any other MultiTasking
> enviroment for that matter) it's ready when the process ends in stead of
> when the prompt is back.
> You could have the shell give a message like: "/dev/fd0 can now be removed
> safely".
> So unless you see that message, do not remove the disk.
Sorry for replying twice, I thought of something else. You say
that I could have the shell give me a message like: "/dev/fd0 can
now be removed...". Why not just let the disk led do that? That
is what the disk LED used to mean before drive caching ruined it
all. I think that the light should STAY on if the disk is being
write cached.
Also, you say that in Linux(or other) that it is ready when the
process ends, however this is not true. I just copied stuff to
my currently mounted floppy. I watched "cp" with "top" until the
process was finished. I got my prompt back and removed the disk.
That disk now needs to be reformatted because the cache is NOT
sync'd before the prompt returns. Even if the cache was sync'd
before the prompt returns in BASH, it won't help me if I'm using
Midnight commander or something else to copy to the disk. Since
caching a floppy is TOTALLY USELESS to me on my system, and just
causes lost disks, I wish I could do away completely with it. I
hope that OpenDOS will also allow this option too.
Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris
Computer Consultant | My webpage has moved and my address has changed.
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
mailto:mharris AT blackwidow DOT saultc DOT on DOT ca
Close windows, and OpenDOS! http://www.caldera.com/dos/dos.htm
- Raw text -