From owner-freebsd-questions@FreeBSD.ORG Thu Jan 29 17:25:57 2004 Return-Path: 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 F18B916A4CE for ; Thu, 29 Jan 2004 17:25:57 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BC6643D45 for ; Thu, 29 Jan 2004 17:25:56 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AAB4C66E32; Thu, 29 Jan 2004 17:25:52 -0800 (PST) Date: Thu, 29 Jan 2004 17:25:52 -0800 From: Kris Kennaway To: Michael Clark Message-ID: <20040130012552.GA69892@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: "'freebsd-questions@freebsd.org'" Subject: Re: 5.1 -> 5.2 disaster X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 01:25:58 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 29, 2004 at 04:16:22PM -0600, Michael Clark wrote: > Assuming that happened somehow, which is hard to believe because I scripted > the process and have upgraded this machine before It's exactly what happened; this user error is reported quite a lot (and I've run into it myself when I have tried to be too clever). You *must* follow the upgrading directions listed in the handbook and UPDATING *precisely*, or you *will* eventually encounter this type of error. Just because you can get away with skipping steps sometimes, does not mean that you'll be that lucky every time. , what can be done to fix > it? Am I on the correct track with using a CD upgrade? A CD upgrade or reinstall should fix it for you. Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAGbKgWry0BWjoQKURAoXTAKCy9enlMV7Gj9lMOS9MsAbkRMoUTACgif1r Y5erJKPN111o+A7skQocoeA= =+Co9 -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--