Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!ur-tut!sunybcs!ugmiker
From: ugmiker@sunybcs.uucp (Michael Reilly)
Newsgroups: comp.sys.amiga
Subject: Re: A FaccII suggestion !?!?
Message-ID: <9279@sunybcs.UUCP>
Date: 14 Mar 88 14:27:04 GMT
References: <2126@mit-amt.MEDIA.MIT.EDU> <9220@sunybcs.UUCP> <224@gtss.UUCP>
Sender: nobody@sunybcs.UUCP
Reply-To: ugmiker@sunybcs.UUCP (Michael Reilly)
Distribution: na
Organization: SUNY/Buffalo Computer Science
Lines: 27
Keywords: FaccII

In article <224@gtss.UUCP> chas@gtss.UUCP (Charles Cleveland) writes:
>Well, couldn't FACC just check the date and time the volume was last altered,
>which is recorded in the disk's boot block, and only keep the old buffers if
>it hadn't changed?
>Charles Cleveland    Georgia Tech School of Physics    Atlanta, GA 30332
>UUCP: ...!gatech!gtss!chas         INTERNET:  chas@ss.physics.gatech.edu

what would happen if one amiga's clock is 5 minutes behind another one, if 
you take a disk out of the one 5 minutes behind, you can actually put a date
on the disk that is BEFORE the last time the disk was written...hmmmmm that 
would be interesting...  I think what you people are trying/hoping to do with
facc is just not what it was designed for....if you have enough memory to be
able to cache a whole disk, why not just load most of it into memory, you can
figure out which of the programs you use on the disk, and which ones are more
important to be in memory... it is of course not automatically caching, but it
would work.....  Maybe we need someway of writing something on a disk that tells
all other computers (amigas) that the disk is "busy" and cant be written on, it
can be read from , but not written onto.... except this is probably more trouble
than it would be worth... :-)

						mike


Mike Reilly  President of UGCSA           University of Buffalo Computer Science
csnet:	ugmiker@buffalo.CSNET 
uucp:	..!{nike|watmath,alegra,decvax}!sunybcs!ugmiker
BITNET:	ugmiker@sunybcs.BITNET   <-OR->   ACSCMPR@ubvmsc.BITNET