From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 10:01:06 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99F7A16A41B for ; Sun, 11 Nov 2007 10:01:06 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 4702113C494 for ; Sun, 11 Nov 2007 10:01:06 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA07.westchester.pa.mail.comcast.net with smtp id BMw21Y0020EZKEL0000C00; Sun, 11 Nov 2007 10:00:44 +0000 Received: from 0lsen.net ([24.20.127.157]) by OMTA01.westchester.pa.mail.comcast.net with comcast id BMzk1Y0023Pt6RU0000000; Sun, 11 Nov 2007 09:59:44 +0000 X-Authority-Analysis: v=1.0 c=1 a=ZOsxE_ufJGOEUTGXnV4A:9 a=BEXLd6SPDmW4dAJ3qhgKL_8a7LgA:4 a=LY0hPdMaydYA:10 Received: by 0lsen.net (Postfix, from userid 1001) id D731B17A53; Sun, 11 Nov 2007 01:59:43 -0800 (PST) Date: Sun, 11 Nov 2007 01:59:43 -0800 From: Clint Olsen To: freebsd-stable@freebsd.org Message-ID: <20071111095943.GA1923@0lsen.net> References: <20071102095628.GA796@0lsen.net> <472AF94B.1020600@gmx.de> <20071111043931.GA1460@0lsen.net> <4736BC01.2000800@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4736BC01.2000800@gmx.de> User-Agent: Mutt/1.4.2.3i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Subject: Re: Ok, so now what? Binary upgrade to 6.2-RELEASE fails 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: Sun, 11 Nov 2007 10:01:06 -0000 On Nov 11, [LoN]Kamikaze wrote: > That's strange, I've gone right from 5.3 through to RELENG_7 without ever > doing the reboots during the install process (I know that's not > recommended) and I never ran into trouble. Did you accidently turn off > compat6x in the kernel before you built? Did your remember to install the > misc/compat6x port? Well, I wasn't upgrading to RELENG_7, so compat6x shouldn't have been an issue. And any compatibility library should not have been necessary when doing a binary upgrade. I was trying to boot a GENERIC kernel in the upgrade process. My 5.5 kernel is only slightly customized as a superset of the original 5.X kernel. I don't have the misc/compat5x installed on my system. I don't remember seeing that in the upgrading section of the handbook, so I didn't do that. I can see this as being necessary for running certain legacy applications, but I should still be able to boot the kernel. Thanks, -Clint