Return to BSD News archive
Xref: sserve comp.os.linux.development:2690 comp.os.386bsd.development:1456 comp.os.386bsd.misc:1598
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!math.ohio-state.edu!cs.utexas.edu!swrinde!dptspd!ephsa!endicor.com!tsarna
From: tsarna@endicor.com (Ty Sarna)
Newsgroups: comp.os.linux.development,comp.os.386bsd.development,comp.os.386bsd.misc
Subject: Re: Has anyone written a Mac FS or Mac FS Access utilities for Linux or 386BSD?
Message-ID: <CGII5I.6Lo@endicor.com>
Date: 15 Nov 93 02:41:40 GMT
References: <CEv6Co.MA1.3@cs.cmu.edu> <CF7M7I.Enw@wg.saar.de> <2a4l4h$bqs@lasalle.cs.columbia.edu> <c9107786.753120740@peach.newcastle.edu.au>
Organization: Endicor Technologies, Inc., San Antonio, Texas
Lines: 23
In article <c9107786.753120740@peach.newcastle.edu.au> c9107786@peach.newcastle.edu.au (David Leonard) writes:
> lih@news.cs.columbia.edu (Andrew "Fuz" Lih) writes:
>
> CAP does that. Its quite a natural thing to do in a UFS, to put things in
> directories. The macintosh file "foo" would appear as:
>
> ./foo (the data fork)
> ./.resource/foo (the resource fork)
> ./.finderinfo/foo (other stuff)
Why not handle it the way isofs does (I believe it makes the resource
fork appear as a file of the same name, but with '=' prepended). It
would be nice to have some consistency in these things.
> I dont think you should nasty up the kernel to handle non-flat (bent?) files,
> just like I dont think you should nasty it up for non-flat memory addr spaces.
I have to agree. Forked files are bad news, IMHO.
--
Ty Sarna "Don Johnson is back -- back in time, and battling
drug-trafficking dinosaurs. Don Johnson -is-
tsarna@endicor.com Jurassic Narc. Tuesdays at 8; 7 Central & Mountain"