Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!newsfeed.direct.ca!hunter.premier.net!op.net!news.mathworks.com!newsfeed.internetmci.com!newsxfer2.itd.umich.edu!news.itd.umich.edu!terminator.rs.itd.umich.edu!wes From: Wesley.Craig@umich.edu Newsgroups: comp.unix.bsd.freebsd.misc,comp.protocols.appletalk Subject: Re: Netatalk or CAP on FreeBSD Date: 6 Aug 1996 14:56:55 GMT Organization: University of Michigan Lines: 14 Message-ID: <4u7mfn$j5h@lastactionhero.rs.itd.umich.edu> References: <girgen-0608960208020001@sl01.modempool.kth.se> NNTP-Posting-Host: terminator.rs.itd.umich.edu Originator: wes@terminator.rs.itd.umich.edu Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:25053 comp.protocols.appletalk:22228 Palle Girgensohn <girgen@partitur.se> wrote: >I cannot verify this myself, but everybody using Netatalk with FreeBSD >(2.1) (including the author) claims that atalkd cannot do seed routing. FreeBSD is not a supported platform for netatalk. That's definitive, no hearsay, I'm the author of netatalk. Mark D. attempted a port of netatalk 1.3.3b2 to FreeBSD 2.x. His kernel changes are now part of a FreeBSD distribution. However, the changes have problems, the kernel can't support netranges on the local wire. We've just got a FreeBSD box up here, and we're going to try to make netatalk work "correctly" on it. :wes