Date: Wed, 27 Feb 2002 13:02:15 -0700 From: "Brigg Angus" <brigg@flatlan.net> To: "Joe Clarke" <marcus@marcuscom.com> Cc: <ports@FreeBSD.ORG> Subject: Re: FreeBSD Port: netatalk-1.5.2 Message-ID: <000f01c1bfc9$a720a230$0b14650a@frithia> References: <20020227145630.W24146-100000@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I should be flogged to death with my own tongue, cut up into many pieces and scattered across the globe, and my name erased form all records. That's the problem. I've got an itchy # finger. My apologies. Best, Brigg ----- Original Message ----- From: "Joe Clarke" <marcus@marcuscom.com> To: "Brigg Angus" <brigg@flatlan.net> Cc: <ports@FreeBSD.ORG> Sent: Wednesday, February 27, 2002 12:57 PM Subject: Re: FreeBSD Port: netatalk-1.5.2 > > > On Wed, 27 Feb 2002, Brigg Angus wrote: > > > Have been trying to get netatalk 1.5.2 to work with little success. I am > > using the same system (FreeBSD 4.5) and configuration of 5 days ago, the > > only difference being the upgrade to netatalk 1.5.2. Errors when starting > > up netatalk are as follows: > > > > socket: Protocol not supported > > atalkd: can't get interfaces, exiting. > > Looks like you're running a kernel without > > options NETATALK > > 1.5.2 works fine on my 4.5-stable machine. > > Joe > > > > > I also log this message (nothing more): > > > > afpd[263]: main: atp_open: Protocol not supported > > > > As I said, v. 1.5.1 worked fine with this same setup. Any suggestions, > > RTFM pointing, etc. would be appreciated. > > > > Best, > > Brigg > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-ports" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01c1bfc9$a720a230$0b14650a>