Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!agate!e260-3f.berkeley.edu!labc-3dc
From: labc-3dc@e260-3f.berkeley.edu (Andy McFadden)
Newsgroups: comp.sys.apple
Subject: Re: GS/OS, CMS60, bugs, etc.
Summary: Ouch.
Message-ID: <19795@agate.BERKELEY.EDU>
Date: 1 Feb 89 20:12:56 GMT
References: <8901301953.aa14656@SMOKE.BRL.MIL>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 16

I was using an older P16 shell under GS/OS when I noticed that somebody failed
to inform GS/OS that I had switched disks.  If you think about it for a minute,
you realize that two volumes with the same name will appear to be the same
volume; if you switch them then GS/OS will use the cached directory.

I managed to trash a disk in this manner; the directory of the first disk
was written onto the second.

I've also heard reports of people who update their files, only to have GS/OS
read from the cache.  I don't have first-hand experience of this, but it
shouldn't be that hard to test (although logically it shouldn't happen if
the cache was implemented correctly).

-- 
labc-3dc@widow.berkeley.edu (Andy McFadden)
c60c-3aw@widow.berkeley.edu (expiring soon)