Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!vax135!cjp
From: cjp@vax135.UUCP (Charles Poirier)
Newsgroups: comp.sys.amiga
Subject: Re: Facc From ASDG
Message-ID: <1796@vax135.UUCP>
Date: Fri, 12-Jun-87 21:53:10 EDT
Article-I.D.: vax135.1796
Posted: Fri Jun 12 21:53:10 1987
Date-Received: Sat, 20-Jun-87 18:36:37 EDT
Reply-To: cjp@vax135.UUCP (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 29
Summary: Cache DISKs, not DRIVEs

(I mailed this to Perry at the well but getting no reply...)

What I want is a DISK cache.  Facc?  That is a DRIVE cache.  Pop out
the disk for any reason, and all those lovely buffers are invalidated.
For people having only one drive, and even for me with two, it's an
all-too-common occurrance to have to drag in a program from elsewhere
than the mounted disk(s).

It would be nice if the cacher remembered my disk names.  It would
remember any disk for which all buffers had not been expired, and
recognize it next time it showed up, regardless of which drive it
showed up in.  Those buffers should still be valid when I pop the disk
back in.  This is what you need for a true disk cache.

Yeah I know, you need some optional escapes to keep from getting burned
over a couple of cases.  Say, same-name but distinct disks.  I think
this can be handled.  If nothing else, there is a relatively unique
disk-id field somewhere on each disk (so I am told).  Say, I take the
disk out, put it in my *second* Amiga ( ;-) ), and change it, then bring
it back.  So you put an escape button in the cacher's window for "new disk".

How hard can this be?  Maybe it is hard, I wouldn't know.  I'm
surprised no one has suggested this before.  Anyone care to second the
motion?

-- 
	Charles Poirier   (decvax,ucbvax,ihnp4,attmail)!vax135!cjp

	"The road to Hell is paved with good opinions."