Subject: Re: resource forks export (was Re: _KERNEL cpp symbol...)
To: Frederick Bruckman <fb@enteract.com>
From: Nathan Raymond <nate@portents.com>
List: port-mac68k
Date: 07/29/1999 09:21:54
At 6:40 AM -0500 7/29/99, Frederick Bruckman wrote:

>On Thu, 29 Jul 1999, Ken Nakata wrote:
>
> > 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?
>
>To change the subject, one thing that annoys me about netatalk is that
>it creates an .AppleDouble/file for every single file, whether it has
>or had a resource fork or not. Does CAP not do that? What is CAP
>anyway? Is that the AppleServer?

CAP is the Columbia AppleTalk Package.  Check out -

ftp://munnari.oz.au/mac/

It's like netatalk, but its not something that sits in the kernel 
(I've heard its a bit slower), but it has numerous add-ons (its 
licensing is also different).  You also have to take a few minutes to 
patch the source up to the current level after downloading (you can't 
just download the latest source, everything is built off patches). 
Some of the coolest things about it are the AppleTalk router, IP 
tunnelling, and the ARA Server add-on (the Sun 3 68k binary seems to 
run fine under netbsd) -

ftp://munnari.oz.au/mac/arns_arap/aarap.sun3.4.1.tar.Z

So in theory I should be able to link two remote AppleTalk networks 
as one (across IP), support dialup AppleTalk (with TCP/IP 
encapsulated in AppleTalk through MacIP for the client), and 
AppleShare IP with the latest patch levels.

If all you need is an AppleShare server, netatalk is probably just as 
good, a little faster, and built-in to netbsd.

--
Nathan Raymond