From owner-freebsd-hackers Wed Nov 3 16:28: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id DF84215653 for ; Wed, 3 Nov 1999 16:27:56 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id SAA18480; Wed, 3 Nov 1999 18:27:08 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Wed, 3 Nov 1999 18:27:08 -0600 (CST) From: David Scheidt To: "Ron 'The InSaNe One' Rosson" Cc: Mark Newton , freebsd-hackers@freebsd.org Subject: Re: (forw) Reversing 32Upgrade package In-Reply-To: <19991103160627.B5752@lunatic.oneinsane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Nov 1999, Ron 'The InSaNe One' Rosson wrote: > On Thu, 04 Nov 1999, Mark Newton was heard blurting out: > > > If it's a production system you will have had backups from immediately > > before your upgrade, and reversing the upgrade will be a simple matter > > of restoring your backups. > > Well the custom software that is running on this box is only geared > for 2.28 at the moment. Backup tapes do you know good if you are not > sure what files got changed and how. Which is the reason for the > question. > In that case the only sane thing to do is assume that every file on the box changed and rebuild it from scratch from the backups. Upgrading will touch nearly everything in /etc, /dev, /sbin/, /usr/bin/, /usr/sbin, /usr/lib, /modules, /usr/include, and so forth. It won't (or shouldn't...) touch antyhing in /usr/local, /home or in any filesystem not mentioned in hier(7). David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message