Date: Sun, 16 Nov 1997 22:42:32 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Eric Anderson <keric@websidestory.com> Cc: questions@FreeBSD.ORG Subject: Re: 2.2.2 -> 2.2.5 upgrade Message-ID: <Pine.BSF.3.96.971116224045.9641B-100000@gdi.uoregon.edu> In-Reply-To: <Pine.BSI.3.96.971114184249.18807J-100000@mail.websidestory.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971116224045.9641B-100000>