Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!ernie!bazyar
From: bazyar@ernie (Jawaid Bazyar)
Newsgroups: comp.sys.apple2
Subject: Re: Reordering GS/OS directories
Message-ID: <1991Jan29.210436.3866@ux1.cso.uiuc.edu>
Date: 29 Jan 91 21:04:36 GMT
References: <15006@smoke.brl.mil> <1991Jan29.113245.24252@nntp-server.caltech.edu> <15014@smoke.brl.mil>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: bazyar@cs.uiuc.edu (Jawaid Bazyar)
Organization: Mutation Testing Facility, University of Illinois
Lines: 23

In article <15014@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>In article <1991Jan29.113245.24252@nntp-server.caltech.edu> toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes:
>>Since the FST's are assumed to be caching blocks whenever they can ...
>
>But all that is required is for the block I/O calls to ask the FSTs
>to flush their caches before proceeding with the block I/O.  In any
>case this is a fixable problem.  (On UNIX it is solved by assuming
>that the filesystem is not mounted during a "raw disk" I/O operation,
>and it is the user's responsibility to ensure this condition.  On
>GS/OS another approach would be required.)

I still fail to see the problem.  How often do you actually have to
do block I/O on a disk drive?  Not very often, you say? Maybe once
or twice a month to check for filesystem inconsistencies?  Is it
too rough to have to boot off of floppy once or twice a month?

sheesh...

--
Jawaid Bazyar               | "I'm sure K&R have never heard of Mike." 
Senior/Computer Engineering |
bazyar@cs.uiuc.edu          | "That's okay. I'm sure Mike's never heard of K&R".
   Apple II Forever!        |  (discussion about Orca/C)