Re: CTree/ETree

[bvf@tiamat.umd.umich.edu (Joshua Thompson)]

In <1993Feb24.092523.8166@gallant.apple.com> dlyons@apple.com (David A Lyons) writes:

>In article <1993Feb13.150743.26979@actrix.gen.nz> ,
>David.Empson@bbs.actrix.gen.nz writes:

>(About the CTree and ETree "open files" that show up for HFS volumes.)

>>Probably just for convenience.  I think the HFS FST has made up the
>>filenames just to be consistent.  I wonder what happens if you try to
>>close them?  :-)

>Exactly, they are for the HFS FST's convenience.  You can't refer to them
>by pathname, because they have full pathnames which are impossible ("
>CTree" and " ETree", which don't start with colons).

>If you try to close them by reference number, you get error $004B, bad
>storage type.

Just out of curiosity, what would happen if we tried to read (or, heaven forbid, WRITE) to those files?  Would we end up reading some wonderful B*Tree nodes or something, or would the operation just return error $004B as well?

(I have a morbid fear of B*Trees...I've had two experiences with manually editing an HFS volume to fix real bad problems that Norton won't fix :)

--
FutureNET : #1@#1                                 "I don't want hear anymore
      AOL : JoshuaT256                            about your stinky fantasies!"
 Internet : thompson@umdsun2.umd.umich.edu                   - Ren Hoek in
            bvf@tiamat.umd.umich.edu                          "Son of Stimpy"