Path: utzoo!attcan!uunet!lll-winken!brutus.cs.uiuc.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!pro-beagle.cts.com!mmunz
From: mmunz@pro-beagle.cts.com (Mark Munz)
Newsgroups: comp.sys.apple
Subject: Re: The FST story continues
Message-ID: <8910101818.AA22722@trout.nosc.mil>
Date: 10 Oct 89 13:45:02 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18

Network Comment: to #11440 by dlyons@apple.com

-> John, I agree with almost everything you said.  I just have to point ou
-> that *writing* to an HFS volume is more complicated than reading it (si
-> you have to rearrange the B-tree (or is it B*-tree?) directory structur
-> whenever you add, delete, or rename a file).  Bugs in *reading* a disk
-> are a nuisance, but any bugs in *writing* could destroy people's volume

 Wait a sec.. you make it sound like you're GUESSING at how the Macintosh
writes its stuff to disk. Last I heard, APPLE had MAC SOURCE on how to read
and write to the disk..  Now the way I see it, it would take a very short time
for someone to convert the MAC SOURCE CODE into 65816-based code.

That's not to say you won't have bugs, but chances are Apple (if they didn't
try to do it from scratch) could put out a fairly reliable HFS FST pretty
quick like.

--Mark Munz