From owner-freebsd-questions@FreeBSD.ORG Fri Jan 16 15:51:28 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6725D23F for ; Fri, 16 Jan 2015 15:51:28 +0000 (UTC) Received: from aura.veggiechinese.net (ns1.veggiechinese.net [66.215.1.146]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DE2F37E for ; Fri, 16 Jan 2015 15:51:27 +0000 (UTC) Received: by aura.veggiechinese.net (Postfix, from userid 1228) id 1AAB35C0F; Fri, 16 Jan 2015 07:51:21 -0800 (PST) Date: Fri, 16 Jan 2015 07:51:20 -0800 From: William Yardley To: freebsd-questions@freebsd.org Subject: Re: ssh_explicit_bzero error on upgrade to 9.3-RELEASE-p8 Message-ID: <20150116155120.GA26753@aura.veggiechinese.net> References: <20150115065251.GC44091@aura.veggiechinese.net> <20150116011339.GJ34531@aura.veggiechinese.net> <95804187-52E2-42D9-B930-F73A2E6F8FFD@buildingonline.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <95804187-52E2-42D9-B930-F73A2E6F8FFD@buildingonline.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 15:51:28 -0000 On Fri, Jan 16, 2015 at 07:19:05AM -0700, Dan Busarow wrote: > The solution below was given to me by Dan Langille for my similar > situation. upgrade to 9.3 from 9.2 that apparently did not upgrade > userland > ---------------------------------------------------------------------- > env UNAME_r=9.2-RELEASE freebsd-update upgrade -r 9.3-RELEASE > freebsd-update install > freebsd-update install Eep - wish I had seen this sooner. I followed the solution implied in the older thread by brute-force untarring the base system tarball (and kernel, after some trial and error). I think I have a working system now, and freebsd-update IDS seems happy with virtually everything that wasn't locally modified, so I'm hopefully up and running again. Thanks for the reply and the pointer to the bug - glad I'm not totally crazy. w