From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 15 00:21:33 2008 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5426F106564A for ; Fri, 15 Aug 2008 00:21:33 +0000 (UTC) (envelope-from mpope@teksavvy.com) Received: from ironport2-out.teksavvy.com (ironport2-out.pppoe.ca [206.248.154.182]) by mx1.freebsd.org (Postfix) with ESMTP id 181988FC0C for ; Fri, 15 Aug 2008 00:21:32 +0000 (UTC) (envelope-from mpope@teksavvy.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoUBAAxppEhFHOS9/2dsb2JhbAAItiOBVQ X-IronPort-AV: E=Sophos;i="4.32,212,1217822400"; d="scan'208";a="25498820" Received: from mbpesecurity.com (HELO [192.168.111.174]) ([69.28.228.189]) by ironport2-out.teksavvy.com with ESMTP; 14 Aug 2008 20:21:31 -0400 Message-ID: <48A4CC0F.1090304@teksavvy.com> Date: Thu, 14 Aug 2008 20:21:35 -0400 From: Matthew User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: kern/120733: libbsm.so.1 missing after upgrading to 6.3-RELEASE X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2008 00:21:33 -0000 Kris, Thanks for your quick response. I did read the Handbook, and googled carefully before I used freebsd-update.sh to migrate from 6.1 to 6.3. (Relevant documentation suggested only minor to minor revision migration was supported, except 6.3 to 7.0 would work.) So I migrated to 6.3 intending to then migrate to 7.0, but I experienced this kern/120733 bug, leaving the 6.3 installation in a disabled state. I did email the person responsible, but it is vacation season after all. Are you (or is anyone) aware of any way to upgrade to 7.0 from the 6.3-RELEASE installation in this disabled state, i.e. without having to do a fresh 7.0 install and a manual port all my application configurations? (Given what happened when I followed the best documentation around, I'm reluctant to experiment.) Thank you, Matthew > Kris Kennaway wrote: >> Matthew wrote: >>> Hello, >>> >>> Given this bug has not changed status since Februrary, can anyone >>> suggest a workaround? >>> My server is now partly disabled after upgrading to 6.3-RELEASE >>> (sshd won't run, etc). 1) Is there anyway to use freebsd-update.sh to jump ahead to 7.0 while 6.3 is in this broken state? >>> >>> 2) Is a fresh install of 7.0, with a manual port of all state from >>> the existing server (bind, httpd, asterisk, etc) the only way to >>> escape this bug? >> >> Use one of the several other methods for installing/updating FreeBSD? >> >> Kris >> > > Also consider sending a followup enquiry to the PR. > > Kris >