Subject: Re: [netatalk-admins] IP-only netatalk [formerly:Network Server 700 and netatalk]
From: a sun (asun@saul5.u.washington.edu)
Date: Mon Apr 06 1998 - 12:33:41 EDT
> Although this might only provide limited capabilities, but what about a
> stripped, TCP/IP only netatalk. There were considerations on the list
> before; has anyone actually started to do it?
okay, here comes another faq type response. somebody archive it for
posterity.
Q: what is an IP only appletalk?
A: you can carry appletalk over ip. however, this is not what is
usually meant by the question. usually, somebody is actually
interested in using appleshare over ip. this, in itself, does not
need appletalk at all although it can use bits to register itself
in the chooser.
Q: what's involved in making netatalk tcp/ip only?
A: the only part of netatalk that can be tcp/ip only is afpd. to do
this and have it work on a particular machine, you need to do two
things:
1) rip out all of the appletalk specific stuff in afpd.
2) munge netatalk/endian.h and etc/afpd/unix.c so that they
work on your machine.
in my current, unavailable patch set, i've done #1 already. the
addition of afp/tcp actually made the job easier by encapsulating
the relevant bits. i'll probably encapsulate things a little more
to reduce the number of ifdefs necessary. the libatalk Makefile
needs to be changed to not build any of the appletalk stuff. to do
#2 correctly, you really need to do a configure type thing. i'll
probably stick in USE_BLAH_H type defines in and have people fiddle
with them until they work..
Q: what do i lose by going to tcp/ip only?
A: tcp/ip based networks don't advertise services. as a result,
you'll need to know the server/printer to which you want to
connect.
-a
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:13 EST