From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 14 06:19:40 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 9B627106567A for ; Thu, 14 Aug 2008 06:19:40 +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 64BF08FC25 for ; Thu, 14 Aug 2008 06:19:40 +0000 (UTC) (envelope-from mpope@teksavvy.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmQBALxqo0hFHOS9/2dsb2JhbAAItTqBVQ X-IronPort-AV: E=Sophos;i="4.32,206,1217822400"; d="scan'208";a="25457827" Received: from mbpesecurity.com (HELO [192.168.111.174]) ([69.28.228.189]) by ironport2-out.teksavvy.com with ESMTP; 14 Aug 2008 02:18:37 -0400 Message-ID: <48A3CE3D.7040905@teksavvy.com> Date: Thu, 14 Aug 2008 02:18:37 -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: 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: Thu, 14 Aug 2008 06:19:40 -0000 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? Many thanks, Matthew