Return to BSD News archive
Xref: sserve comp.os.linux.development:2722 comp.os.386bsd.development:1477 comp.os.386bsd.misc:1623
Newsgroups: comp.os.linux.development,comp.os.386bsd.development,comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!extro.ucc.su.OZ.AU!geoffw
From: geoffw@extro.ucc.su.OZ.AU (Geoffrey Warren Hicks)
Subject: Re: Has anyone written a Mac FS or Mac FS Access utilities for Linux or 386BSD?
Message-ID: <geoffw.753500028@extro.ucc.su.OZ.AU>
Sender: news@ucc.su.OZ.AU
Nntp-Posting-Host: extro.ucc.su.oz.au
Organization: Information Services, Sydney University, Sydney, NSW, Australia
References: <CEv6Co.MA1.3@cs.cmu.edu> <29otpb$s8a@news.u.washington.edu> <29vld0$n11@news.delphi.com> <CF7M7I.Enw@wg.saar.de> <2a4l4h$bqs@lasalle.cs.columbia.edu> <c9107786.753120740@peach.newcastle.edu.au>
Date: Wed, 17 Nov 1993 01:33:48 GMT
Lines: 49
Posted on behalf of Craig Southeren who does not have access to
a net account:
-------------------------------------------------------------------
c9107786@peach.newcastle.edu.au (David Leonard) writes:
>lih@news.cs.columbia.edu (Andrew "Fuz" Lih) writes:
>>In article <CF7M7I.Enw@wg.saar.de>, Patrick Schaaf <bof@wg.saar.de> wrote:
>>>cshaulis@news.delphi.com (CSHAULIS@DELPHI.COM) writes:
>>>>[on MAC files and their forks, and how they might map to files under Linux]
>>>
>>>Would it be a Bad Thing to have files that, in addition to being a normal
>>>file (the data fork), implement the various directory ops? i.e. access the
>>>data fork as 'foo`, and other forks as 'foo/thingie` and so on?
>>>
>>>having strange ideas...
>>Not so strange: that's how the Apple UNIX File System in the Columbia
>>AppleTalk Package does it. It's been in active use for over 5 years now.
>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)
>The group and owner of the file are used for the Sharing stuff (naturally)
>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.
>What would also be tricky is a program similar to AccessPC for the Mac that
>possibly supplemented the Install program provided with the ALICE project,
>that would allow you to mount a UFS under MacOS. I guess all this will come
>in Time.
I'm currently working on an "mtools"-like package to access Mac disks
from Linux. Having used CAP & Access PC on the Macs, and other Unix systems,
you find that 99% of the time you don't care about the resource fork.
So spending lots of time to make access to resource forks real easy by
creating a forked filesystem is a waste of time. I'll be using the CAP
approach, or something very similar.
Craig