From owner-freebsd-stable@FreeBSD.ORG Fri Oct 21 18:20:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 30A5B16A41F for ; Fri, 21 Oct 2005 18:20:05 +0000 (GMT) (envelope-from dick@nagual.st) Received: from nagual.st (cc20684-a.assen1.dr.home.nl [82.74.2.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87FC043D46 for ; Fri, 21 Oct 2005 18:20:04 +0000 (GMT) (envelope-from dick@nagual.st) Received: from pooh.nagual.st (pooh.nagual.st [192.168.11.22]) by nagual.st with esmtp; Fri, 21 Oct 2005 20:20:02 +0200 id 00000028.43593152.00003BB4 Date: Fri, 21 Oct 2005 20:21:27 +0200 From: dick hoogendijk To: freebsd-stable@freebsd.org Message-Id: <20051021202127.30c0d3f3.dick@nagual.st> In-Reply-To: <20051019225351.GA77421@xor.obsecurity.org> References: <200510152346.RAA20742@lariat.net> <20051016135752.6bcc6874.dick@nagual.st> <20051019231046.1136a1ea.dick@nagual.st> <20051019225351.GA77421@xor.obsecurity.org> Organization: de nagual X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 6.0 release date and stability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Oct 2005 18:20:05 -0000 On Wed, 19 Oct 2005 18:53:51 -0400 Kris Kennaway wrote: > On Wed, Oct 19, 2005 at 11:36:35PM +0200, Ronald Klop wrote: > > COMPAT_FREEBSD5 is meant for running FreeBSD-5 binary applications. > > If you have them it's ok. If you recompile everything you don't > > need the COMPAT_FREEBSD5 stuff. If you don't have the source of > > some of your FreeBSD-5 applications you have to run with > > COMPAT_FREEBSD5. And the switch to 6 is easier because your > > 5-applications keep running. > > Yes. As long as you only use your old 5.x applications, you're fine > with just the compat. The problem is when you start to link *new* 6.0 > applications with *old* 5.x libraries (e.g. by installing a new port, > e.g. a new X application, without rebuilding your 5.x X installation > first). > > Thus, unless you upgrade all your 5.x ports (well, actually "many", > i.e. only those that provide libraries or shared object modules, but > it's easier to just do "all") you'll end up with 6.0 binaries that are > linked to e.g. two versions of libc at once (the 5.x libc and the 6.0 > libc), which is a recipe for disaster. I learn much from these kind of answers. Thanks Kris. What I don't get is how I can /get rid/ of these old 4.x / 5.x libraries on my "new" updated 6.0 system. I guess teh way to go is: cvsup to the latest 6.0 source; do the well-known buildworld thing; rebuild the kernel without compat_freebsd4/5 option (???) and rebuild every port with portupgrade -fa But he old libraries are still on the system than, aren't they? Or will they not be used and if not, why? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja