From owner-freebsd-current Fri Nov 8 10:42:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD58C37B401 for ; Fri, 8 Nov 2002 10:42:19 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CFCF43E6E for ; Fri, 8 Nov 2002 10:42:19 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.6/8.12.6) with ESMTP id gA8IgF8A071555; Fri, 8 Nov 2002 10:42:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.6/8.12.6/Submit) id gA8IgFv4071554; Fri, 8 Nov 2002 10:42:15 -0800 (PST) Date: Fri, 8 Nov 2002 10:42:15 -0800 From: Steve Kargl To: Andrew Kenneth Milton Cc: Daniel Eischen , "M. Warner Losh" , ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021108184215.GA71377@troutmask.apl.washington.edu> References: <20021108.092732.124899267.imp@bsdimp.com> <20021108174915.GA71225@troutmask.apl.washington.edu> <20021108181611.GA90784@zeus.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021108181611.GA90784@zeus.theinternet.com.au> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Nov 09, 2002 at 04:16:11AM +1000, Andrew Kenneth Milton wrote: > > 6. Assume Crash Position. > Thanks for your important contribution to a discussion which is addressing a rather serious problem. Here's the important part of the "Ghost..." thread. The following 4.7 libs make reference to __sF. libalias.so.4 libbz2.so.1 libc.so.4 libc_r.so.4 libcam.so.2 libcom_err.so.2 libcrypto.so.2 libdes.so.3 libdevstat.so.2 libdialog.so.4 libedit.so.3 libfetch.so.3 libftpio.so.5 libg2c.so.1 libgmp.so.3 libhistory.so.4 libipsec.so.1 libisc.so.1 libkdb.so.3 libkrb.so.3 libkrb5.so.5 libkvm.so.2 libm.so.2 libmp.so.3 libncp.so.1 libncurses.so.5 libopie.so.2 libpam.so.1 libpcap.so.2 libperl.so.3 libreadline.so.4 libroken.so.5 libskey.so.2 libsmb.so.1 libssh.so.2 libstdc++.so.3 libutil.so.3 Here's the fun part. The following 5.0 libraries have the same version number as their 4.x counterparts. Try running a 4.x app linked against one of these libaries on a 5.0 machine. You should also note that this list may not be complete list of libraries suffering this problem. libalias.so.4 libbz2.so.1 libcam.so.2 libcom_err.so.2 libcrypto.so.2 libdes.so.3 libdialog.so.4 libfetch.so.3 libftpio.so.5 libg2c.so.1 libhistory.so.4 libipsec.so.1 libisc.so.1 libkvm.so.2 libm.so.2 libncp.so.1 libncurses.so.5 libopie.so.2 libpcap.so.2 libreadline.so.4 libsmb.so.1 libssh.so.2 libutil.so.3 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message