Subject: resource forks export (was Re: _KERNEL cpp symbol...)
To: None <wrstuden@nas.nasa.gov>
From: Ken Nakata <kenn@synap.ne.jp>
List: port-mac68k
Date: 07/29/1999 18:58:39
On Wed, 28 Jul 1999 11:53:34 -0700 (PDT), Bill Studenmund <wrstuden@nas.nasa.gov> wrote:
> On Wed, 28 Jul 1999, Ken Nakata wrote:
> > BTW, are netatalk and CAP different in treatment of the resource fork?
> > I vaguely remember CAP looks into .resource/file (or s/t like that)
> > for file's resource fork (my college uses CAP to export UNIX home
> > directories to Macs).  Oh, well.  I think I'm asking this question way
> > too early.
> 
> netatalk and CAP do treat the resource forks differently. Paul Hargrove's
> hfsfs will actually export the resource forks differently as per mount
> options. :-)

You mean, hfsfs exports the resource forks in either netatalk way or
CAP way?

Well, anyway, that'll come in much later.  We need a data-fork-only
implementation of hfs first, I guess.

Ken