From owner-freebsd-questions Sun Nov 16 22:42:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16425 for questions-outgoing; Sun, 16 Nov 1997 22:42:37 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16419 for ; Sun, 16 Nov 1997 22:42:34 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id WAA09651; Sun, 16 Nov 1997 22:42:32 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Sun, 16 Nov 1997 22:42:32 -0800 (PST) From: Doug White Reply-To: Doug White To: Eric Anderson cc: questions@FreeBSD.ORG Subject: Re: 2.2.2 -> 2.2.5 upgrade In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 14 Nov 1997, Eric Anderson wrote: > > UNDER NO CIRCUMSTANCES UPGRADE ANY MACHINE ON ANY 3.0-SNAPS. YOU WILL > > BREAK THEM IF YOU DO. The mount() system call semantics were changed and > > if you downgrade them to 2.2.x you won't be able to mount your disks > > except from the appropriate fixit floppy. > > So are we screwed with the SNAP versions as far as upgrades go? I reread that and I should have qualified ``upgrade'' to mean ``upgrading'' to 2.2.x-branch RELEASEs. You can safely upgrade any 3.0 SNAP to any future 3.0 SNAP or -CURRENT. > And how does the upgrade from the boot disk affect any configuration > files (such as in /etc)? It does as it does now, it puts files to be updated in /etc/upgrade and lets you merge them in as you desire. I think :-) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major