From owner-freebsd-current@FreeBSD.ORG Fri Jan 9 09:27:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB38106564A; Fri, 9 Jan 2009 09:27:31 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.freebsd.org (Postfix) with ESMTP id CB6038FC14; Fri, 9 Jan 2009 09:27:30 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from acrux.dbai.tuwien.ac.at (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 94FF13910A; Fri, 9 Jan 2009 10:27:28 +0100 (CET) Received: by acrux.dbai.tuwien.ac.at (Postfix, from userid 1203) id 09C5C10059; Fri, 9 Jan 2009 10:27:29 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by acrux.dbai.tuwien.ac.at (Postfix) with ESMTP id EB7F310054; Fri, 9 Jan 2009 10:27:29 +0100 (CET) Date: Fri, 9 Jan 2009 10:27:29 +0100 (CET) From: Gerald Pfeifer To: "Li, Qing" In-Reply-To: Message-ID: References: <20081227202117.F3B14341A3@cavin02.kulnet.kuleuven.ac.be><200812281613.49404.tijl@ulyssis.org> User-Agent: Alpine 1.99 (LSU 1142 2008-08-13) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 09 Jan 2009 12:27:38 +0000 Cc: Tijl Coosemans , freebsd-net@freebsd.org, freebsd-current@freebsd.org, Qing Li Subject: RE: HEADSUP: arp-v2 has been committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2009 09:27:31 -0000 On Tue, 30 Dec 2008, Li, Qing wrote: > I don't think we can provide binary compatibility without putting > back RTF_LLINFO exactly as it was. My preference is to continue down > the new path without RTF_LLINFO. So, you are saying that applications built on FreeBSD 7 or earlier that use RTF_LLINFO will no longer work properly on FreeBSD 8 after your change? Ignoring everything else, that would be a killer and the one reason to definitely change the current situation. Otherwise, ISVs will need two builds, one for FreeBSD 7 and earlier and one for FreeBSD 8, and believe me, that is bad, bad, bad. Or rather: unlikely. (GNU/Linux distributions do provide this level of compatibility.) > We still have some time before the 8.0 release. It's straightforward > for me to retain some of the RTF_LLINFO support in the new kernel if > and when the situation becomes necessary. Sounds like that is the case? > Since the affected ports now have the conditional code around > RTF_LLINFO, the updates would allow these ports to compile in > both -current and in the previous releases. emulators/wine still is broken, and upstream Wine has not accepted the patch yet. I believe one reason likely is the above, and the fact that this may break commercial builds of Wine. How are you going to address this? Gerald -- Gerald (Jerry) Pfeifer gerald@pfeifer.com http://www.pfeifer.com/gerald/