Thanks for the help!  I went with the precompiled netatalk 1.5.3.1 package
and replaced the netatalk-asun.  I haven't advanced to 'rolling' my own yet
:).  I followed the setup messages left at the end of the netatalk install
and all works fine now.

The google searches and netatalk web pages I found pointed my to the asun
package if I wanted to connect from OS X, but I guess either Jaguar or
netatalk 1.5+ have eliminated that obstacle.

Now on to installing Samba - wish me luck!

Cheers,
Bhavesh


on 2/14/03 10:47 PM, Michael G. Schabert at mikeride@mac.com wrote:

>> Sounds like a bug in the script. They're not supposed to do anything
>> if you don't have
>> 
>> atalkd=YES
>> afpd=YES
>> papd=YES
>> 
>> and maybe
>> 
>> timelord=YES
>> 
>> or
>> 
>> timelord=NO
>> 
>> I think that's fixed in netatalk-1.5.5, the latest version.
> 
> For the -asun package, I've just always had
> "/usr/pkg/etc/rc.d/netatalk" in my rc.local.
> 
>> Try using the *netatalk* package. I don't even know why we're still
>> keeping the obsolete versions in netatalk-asun and netatalk-umich
>> around. A quick look at the home page on SourceForge shows that even
>> that package is out-of-date -- they'are at 1.6.0 already -- but 1.5.5
>> is probably your best bet. The package you're using was released
>> before Darwin was even thought of.
> 
> On my alpha, I tried updating from netatalk-asun to netatalk about a
> month ago (1.6k). I deleted the netatalk-asun package and installed
> the netatalk-proper package. After that, my connections from my OS9.1
> clients were flaky and large transfers would fail. Reversing my
> delete/install to -asun fixed the problem.
> 
> Just my thoughts,
> Mike