Hi all.
I hate to bother this list with non-port-mac68k-specific questions, but I
know that there has been some discussion about Netatalk recently. I run
netatalk 1.4.2 with Adrian Sun's patches, and most of the stuff seems to be
working OK. However, when atalkd starts, it spews out a gazillion lines like
atalkd [xxx]: route: n -> 33728.128 Network not reachable
where n goes from 1 to 10, and the from some high number (I think starting
on the low limit of our network range) to the high limit of out network
range. 33728 is our network number, and from the atalkd.conf file atalkd
writes, it seems to get most of the information correctly from the router.
I started by not having any atalkd.conf at all, but that caused a lot of
failures that invlolved the interface eon0. Having a atalkd.conf file
mc0
seems to make it behave better. Oddly enough, I get the same long list of
"Network not reachable" when I kill atalkd.
I did a (quick) search on the netatalk pages for infromation, but did not
find anything useful. I'm running NetBSD 1.3.2, GENERIC-80 on a Q840AV. I
don't know much more about our Appletalk network- I'm sorry.

Please feel free to respond via e-mail if this question is grossly off-topic.

ObPort-mac68k: Is -current broken for anyone else? I get a panic "NO_WAIT
needed" during bootup.

Regards,
/hcb

---
Hans-Christian Becker (hcb@phc.chalmers.se)
Dept. of Physical Chemistry
Chalmers University of Technology
Sweden