Date: Sun, 2 Feb 2003 11:54:56 -0600 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Kevin Day <toasty@dragondata.com> Cc: freebsd-current@freebsd.org Subject: Re: Using 4.3-RELEASE's libc on 5.0 causes hard lockups Message-ID: <20030202175456.GC36076@opus.celabo.org> In-Reply-To: <5.1.1.5.2.20030202114819.044fd230@127.0.0.1> References: <5.1.1.5.2.20030202112759.0461fcc8@127.0.0.1> <5.1.1.5.2.20030202112759.0461fcc8@127.0.0.1> <5.1.1.5.2.20030202114819.044fd230@127.0.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 02, 2003 at 11:53:22AM -0600, Kevin Day wrote: > Ok, I admit, no matter how it happened, an application using the wrong libc > is a bad thing. > > But, how are things supposed to work? Apps that need the old libc.so.4 will find it in /usr/lib/compat/libc.so.4 (or /usr/lib/libc.so.4 if you didn't remove it, for that matter). [...] > In any case, a system lockup or being able to crash other user's processes > just by having the wrong libc shouldn't be possible no matter what happens. Probably not, although if you have processes running as root and using the `wrong' libc, all bets are off. Cheers, -- Jacques A. Vidrine <nectar@celabo.org> http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030202175456.GC36076>