From owner-freebsd-current@FreeBSD.ORG Wed Jul 30 09:47:18 2008 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 A250C1065691 for ; Wed, 30 Jul 2008 09:47:18 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 3B25B8FC23 for ; Wed, 30 Jul 2008 09:47:18 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-023-173.pools.arcor-ip.net [88.66.23.173]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1KO8H707XT-0004vV; Wed, 30 Jul 2008 11:47:17 +0200 Received: (qmail 22939 invoked from network); 30 Jul 2008 09:47:16 -0000 Received: from fbsd8.laiers.local (192.168.4.151) by laiers.local with SMTP; 30 Jul 2008 09:47:16 -0000 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Wed, 30 Jul 2008 11:47:14 +0200 User-Agent: KMail/1.9.52 (FreeBSD/8.0-CURRENT; KDE/4.0.83; i386; ; ) References: <1217346345.12322.31.camel@bauer.cse.buffalo.edu> <200807300247.34948.david@vizion2000.net> In-Reply-To: <200807300247.34948.david@vizion2000.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807301147.15039.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19bahg9a5nZoziIVt44C/jaydyaoPFooECum+L vZNNdmg4zphJoWjqLjkAVeYF5nx2Keg27n+mIAMQD4UCcRtWc4 qod8sBbA5wiFMSOZvnxbg== Cc: Ken Smith , David Southwell , freebsd-current Subject: Re: Upcoming ABI Breakage in RELENG_7 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: Wed, 30 Jul 2008 09:47:18 -0000 On Wednesday 30 July 2008 11:47:34 David Southwell wrote: > On Tuesday 29 July 2008 08:45:45 Ken Smith wrote: ... > For those of us who are not as well informed and experienced as others > could someone please explain what is meant by an ABI breakage, its > implications and how to deal with them. An Application Binary Interface (ABI) breakage means a change of a complex datatype, or a function prototype - in C usually the change of a struct in size or field sort order. This change will effect all consumers of this Interface unless they are recompiled with the changed header files to also use the new interface. The impact depends greatly on the interface that is being changed. As Ken described in the initial mail this change is in the filesystem/vnode layer interface and thus will (only) concern consumers of that ABI. The changed interface is also a kernel-only interface - that means that only 3rd party kernel modules will be affected. I personally don't know of any 3rd party modules that muck about with filesystems (for which you can't get the source). That said, you might have to rebuild stuff like fuse after the breakage has happened. I assume that port maintainers of affected (kernel module) ports will bump the port revision after the change to give you/portupgrade a hint. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News