Message-Id: <199702131820.TAA16620@magigimmix.xs4all.nl>
From: "yeep" <yeep AT xs4all DOT nl>
Cc: "'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject: [opendos] Re: [opendos-developer] Caching
Date: Thu, 13 Feb 1997 18:59:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

> Nothing at all.  The code *should* be inside the device driver or
> whatever just as you state, however I'm talking about removeable
> disks that could be yanked out before someone unmounts them, thus
> the cache software doesn't get a chance to unmount the drive.  I
> guess the cache software is what should be responsible. In other
> words, by using the current method of picking which drives get
> cached, you could enable/disable caching on removable media as
> you see fit.  I think that the default behavior of the disk cache
> should be to not cache any removeable disks though.

I read something, I think it was the cacher supplied in OD, that when the
prompt is back on the screen, the cache has been dumped.
In linux this will be when the process ends I guess.
In other words: You play a game from floppy (don't laugh! It's just an
example) and you quit, after saving your hi-score ofcourse.
The program ends, the cacher get's a signal from the shell(?) and dumps all
delayed-write-stuff to the disk, then gives the user a prompt, which
indicated that the floppy can be removed safely.
This does not mean however that a floppy cacher is useful :-)

	Yeep