Date: Mon, 13 Nov 2000 09:27:08 -0800 (PST) From: John Polstra <jdp@polstra.com> To: stable@freebsd.org Cc: asami@freebsd.org Subject: Re: libc shlib version Message-ID: <200011131727.eADHR8c42388@vashon.polstra.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011131727.eADHR8c42388>