From owner-freebsd-stable@FreeBSD.ORG Fri Mar 4 05:12:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B80616A4CE for ; Fri, 4 Mar 2005 05:12:49 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C15D943D2F for ; Fri, 4 Mar 2005 05:12:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j245EjSZ008343; Thu, 3 Mar 2005 22:14:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4227EDC6.20909@samsco.org> Date: Thu, 03 Mar 2005 22:10:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: msch@snafu.de References: <200503031618.34635.msch@snafu.de> In-Reply-To: <200503031618.34635.msch@snafu.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: freebsd-stable@freebsd.org Subject: Re: ABI broken for 5.4-PRERELEASE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 05:12:49 -0000 Matthias Schuendehuette wrote: > Hi, > > yesterday (MAR02,2005) I updated to 5.4-PRERELEASE. Since then, > 'xsysinfo-1.4a' doesn't run anymore. > > The error message is: "xsysinfo: undefined symbol: _nfiles" > > I had the belief, that this does not happen within a major release of > FreeBSD... isn't it? This looks like an accident. John Baldwin committed a fix to RELENG_5 a few hours ago, so if you can update and retest, it would be appreciated. Note the xsysinfo gropes around in KVM, which is highly fragile. Most of the information that it's looking for is available via sysctl's, which are a lot more stable and reliable. It would be nice if xsysinfo was changed to use these instead. Scott