From owner-freebsd-stable  Mon Nov 13  9:27:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74])
	by hub.freebsd.org (Postfix) with ESMTP
	id 40F8537B4C5; Mon, 13 Nov 2000 09:27:10 -0800 (PST)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA06083;
	Mon, 13 Nov 2000 09:27:08 -0800 (PST)
	(envelope-from jdp@wall.polstra.com)
Received: (from jdp@localhost)
	by vashon.polstra.com (8.11.0/8.11.0) id eADHR8c42388;
	Mon, 13 Nov 2000 09:27:08 -0800 (PST)
	(envelope-from jdp)
Date: Mon, 13 Nov 2000 09:27:08 -0800 (PST)
Message-Id: <200011131727.eADHR8c42388@vashon.polstra.com>
To: stable@freebsd.org
From: John Polstra <jdp@polstra.com>
Cc: asami@freebsd.org
Subject: Re: libc shlib version
In-Reply-To: <vqcd7g09vtq.fsf@silvia.hip.berkeley.edu>
References: <31309.974061923@winston.osd.bsdi.com> <200011130413.eAD4DKj41211@vashon.polstra.com> <vqcd7g09vtq.fsf@silvia.hip.berkeley.edu>
Organization: Polstra & Co., Seattle, WA
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thinking about this some more ... does the upgrade kit contain a new
libc?  It's hard for me to see how these errors could happen if it
didn't.  If it contains a new libc, that seems like the real problem
to me.  It's always risky to use new libs (especially libc) with an
old kernel.

John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message