After some trouble , I finally got netatalk 2.0.3 compiled and installed
(Solaris 10u5 on a X4140) but its kernel module fails to load. Basically,
things are as described on
http://www.unixzone.dk/unix/20060122/appletalk-on-solaris
I had to do a little more to get it compiled and "make kinstall" didn't
work - so I copied ddp and ddp.conf manually and issued the remaining
commands from the Makefile. The error message is exactly the same as
mentioned on the page (relocation error) and ...
... I was hoping that a reboot might help but this was a bad idea. It
started with "Couldn't configure IPv4 interface nge0", and Solaris seemed
to be completely corrupted. I can't see a direkt link between the two
things ...
Anybody git that running?
TIA
fw
> http://www.unixzone.dk/unix/20060122/appletalk-on-solaris
Do you really need the kernel module? Its only for talking direct appletalk
over the wire to machines. This is rarely if ever used with any
current or even halfways-current Mac networks. It'd only be used with
ancient technology (earlier than MacOS 7.6 IIRC).
Most Macs talk Appletalk over Ethernet and have for quite some time.
You don't need the kernel module to support AoE, it works just fine
for me on my home Solaris 10 fileserver.
KCFLAGS= -D_KERNEL -m64
OPTOPTS= -fast -xO5 -xstrconst
CSHAREDFLAGS= -KPIC
LDSHARED= cc
LDSHAREDFLAGS= -G
LDFLAGS_EXPORT=
--
I think this may also work:
---
CC = gcc
LD = ld
# use gcc
KCFLAGS = -D_KERNEL -Di386 -Wall -Wstrict-prototypes ${KGCCFLAGS} -m64 -mcmodel=kernel
OPTOPTS = -O
CSHAREDFLAGS = -fPIC
LDSHARED = ${CC}
#LDSHAREDFLAGS = -shared
LDSHAREDFLAGS = -shared -64
---
Thomas
>Do you really need the kernel module? Its only for talking direct appletalk
>over the wire to machines. This is rarely if ever used with any
>current or even halfways-current Mac networks. It'd only be used with
>ancient technology (earlier than MacOS 7.6 IIRC).
Really? Well, I don't know much about AppleTalk, even though I"m a Mac
user. This is for a customer who has some old Macs running OS 9.
So I can just skip the kernel module? I'll try that.
Thanks so far.
fw
The netatalk documentation has some cavaets about using Appletalk or
not using Appletalk. Its not the easiest terminology to grasp reading
it without background, but you could implement and see how things work
without the atalkd working and just doing afpd.
>The netatalk documentation has some cavaets about using Appletalk or
>not using Appletalk. Its not the easiest terminology to grasp reading
>it without background, but you could implement and see how things work
>without the atalkd working and just doing afpd.
THe machine is now freshly installed. atalkd seems to require ddp?
root@andromeda # /opt/netatalk/sbin/atalkd
can't establish STREAMS plumbing, exiting.
root@andromeda #
Is this caused by the missing entry in /etc/netconfig which refers to /dev/ddp?
TIA
fw
Note, atalkd is the daemon talks Appletalk. This is what I was saying
that you may not need pure Appletalk... Yes, atalkd needs the kernel module.
You are most likely interested in afpd and having it run. This is the
protocol for Macs to mount AFP file shares. atalkd may not be needed
at all..
>Note, atalkd is the daemon talks Appletalk. This is what I was saying
>that you may not need pure Appletalk... Yes, atalkd needs the kernel module.
>
>You are most likely interested in afpd and having it run. This is the
>protocol for Macs to mount AFP file shares. atalkd may not be needed
>at all..
Thanks - that's what I thought after your first reply. Currently, afpd
starts but complains
Jul 1 17:40:15 andromeda afpd[26160]: [ID 702911 daemon.error]
DSIConfigInit: Error registering afp://...:548/?NAME=andromeda&ZONE= with
SRVLOC
Jul 1 17:42:55 andromeda afpd[26189]: [ID 702911 daemon.error] main:
atp_open: Protocol not supported
Will this be a problem?
TIA
fw
>Jul 1 17:40:15 andromeda afpd[26160]: [ID 702911 daemon.error]
>DSIConfigInit: Error registering afp://...:548/?NAME=andromeda&ZONE=
>with SRVLOC
>Jul 1 17:42:55 andromeda afpd[26189]: [ID 702911 daemon.error] main:
>atp_open: Protocol not supported
The second line disappears with "-noddp" in afpd.conf - the first one is
still there.
fw