From owner-freebsd-hackers Tue Jun 23 14:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15470 for freebsd-hackers-outgoing; Tue, 23 Jun 1998 14:48:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rrz.Hanse.DE (rrz.Hanse.DE [193.174.9.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15391 for ; Tue, 23 Jun 1998 14:48:09 -0700 (PDT) (envelope-from stb@hanse.de) Received: from daemon.Hanse.DE (daemon.Hanse.DE [193.174.9.17]) by rrz.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA06211; Tue, 23 Jun 1998 23:41:44 +0200 (CEST) (envelope-from stb@hanse.de) Received: from transit.hanse.de (transit.Hanse.DE [193.174.9.161]) by daemon.Hanse.DE (8.8.8/8.8.8) with ESMTP id XAA13918; Tue, 23 Jun 1998 23:48:06 +0200 (CEST) (envelope-from stb@hanse.de) Received: from localhost (stb@localhost) by transit.hanse.de (8.8.8/8.8.8) with SMTP id XAA13532; Tue, 23 Jun 1998 23:47:27 +0200 (CEST) X-Authentication-Warning: transit.hanse.de: stb owned process doing -bs Date: Tue, 23 Jun 1998 23:47:27 +0200 (CEST) From: Stefan Bethke To: Julian Elischer cc: hackers@FreeBSD.ORG, netatalk@umich.edu Subject: Re: [patch] netatalk broken in 3.0 In-Reply-To: <3585D9A8.15FB7483@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Jun 1998, Julian Elischer wrote: > The netatalk port for FreeBSD doesn't work on FreeBSD because of an > apparently gratuitous change in the 3.0 kernel. Wrong. > in 3.0 you need to use a correct AF_LINK sockaddr (sockaddr_dl) > for setting a hardware multicast address. In most other systems > including 2.2.x this is a AF_UNSPEC (as used by arp). Right. > this patch patches two files in the etc/atalkd directory of netatalk. I believe this is functional eqivalent to the two patches already present, which I took off of the netatalk patches page. (patches/patch-ad and -ae, taken from http://www.umich.edu/~rsug/netatalk/patches) Both patches have since been verified to solve the problem. I cannot say for sure they do with a recent -current; I'm currently making world, so I will know by the end of the week. I will put your newer patches in the next time I touch the port. > can someone who knows how to fix ports commit it? Sure. Why didn't you ask me as the maintainer in the first place? Cheers, Stefan -- Stefan Bethke Muehlendamm 12 Phone: +49-40-256848, +49-177-3504009 D-22087 Hamburg Hamburg, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message