From owner-freebsd-questions@FreeBSD.ORG Tue May 30 22:13:48 2006 Return-Path: X-Original-To: questions@FreeBSD.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9546516AC93 for ; Tue, 30 May 2006 22:13:48 +0000 (UTC) (envelope-from dev@freedomcircle.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41A7743D4C for ; Tue, 30 May 2006 22:13:48 +0000 (GMT) (envelope-from dev@freedomcircle.net) Received: from [192.169.1.3] ([71.101.6.8]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J03007CGN2ZZVI1@vms046.mailsrvcs.net> for questions@FreeBSD.org; Tue, 30 May 2006 17:13:47 -0500 (CDT) Date: Tue, 30 May 2006 18:14:32 -0400 From: Joe In-reply-to: <20060530213344.GA34025@xor.obsecurity.org> To: Kris Kennaway Message-id: <447CC3C8.9020300@freedomcircle.net> Organization: Freedom Circle, LLC MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <447B86F3.6070500@freedomcircle.net> <20060530002535.GA94917@xor.obsecurity.org> <447CB067.1080309@freedomcircle.net> <20060530213344.GA34025@xor.obsecurity.org> User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) Cc: questions@FreeBSD.org Subject: Re: pkg_upgrade? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2006 22:13:49 -0000 Kris Kennaway wrote: > On Tue, May 30, 2006 at 04:51:51PM -0400, Joe wrote: >> [...] >> It failed to update expat however, because it kept looking in the >> 6.0-RELEASE paths. I presume this is because even though the binary >> upgrade of the base to 6.1 went well, uname, etc., think I still have a >> 6.0 machine. So where is the *real* version id stored and how can it be >> (should it be?) safely modified? > > It's reported by the kernel, so if it's still saying 6.0-RELEASE then > that's what you're still running. I don't have access to the system right now, but after the sysinstall I looked at some of the files in /bin and saw that most had a date of May 6, 2006 (or thereabouts) so I assumed that meant the binary upgrade had been successful. How can I verify that the actual kernel was upgraded? Also, I haven't been able to locate much information about a binary upgrade in the Handbook. The only reference was in the INSTALL.htm in the release directory. Joe