From owner-freebsd-questions Thu Jan 23 00:11:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA05949 for questions-outgoing; Thu, 23 Jan 1997 00:11:33 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA05944 for ; Thu, 23 Jan 1997 00:11:30 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.4/8.6.12) with SMTP id AAA23585; Thu, 23 Jan 1997 00:11:23 -0800 (PST) Date: Thu, 23 Jan 1997 00:11:23 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: "Dave A. Roger" cc: freebsd-questions@freebsd.org Subject: Re: Upgrade from 2.1.5 to higher release In-Reply-To: <3.0.1.16.19970117130353.4fdf83d0@mail.tisc.titan.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 17 Jan 1997, Dave A. Roger wrote: > Just recieved my 2.1.6 cdrom and want to remain current. In the past I was > at 2.0.5 and upgraded to 2.1.5 and was overwelmed at the change. It took me > several days and nights to stablize the system from the change/upgrade. > > I reviewed the WEB documents, but did not fine a mention of UPGRADING. > > I am pleased to see the upgrade and fixes being released. I suggest there > be a Handbook page or Document relating just to the process of upgrading > from a prior release, or maybe I missed it... If so, please can you point > me to it? I guess it's time to sgmlize this. FreeBSD Upgrade Checklist: 1) BACKUP /ETC, BACKUP /ETC, BACKUP /ETC. IT __WILL__ BE MODIFIED!!! 2) Boot the new floppy. Select the 'update' option. Follow the prompts. Make sure you MOUNT your filesystems and not NEWFS them. Select the same distributions you did originally and any you wish to add. 3) Hit 'commit'. Take note of the modified files. 4) WHen you're dumped to a shell prompt: . Copy services back from your backup /etc. It's three lines long now :( . Edit sysconfig and re-config from scratch using your old one as a guide. . Migrate any changes you made to rc.local and other files noted during the upgrade process. 5) Reboot, recompile & reinstall your kernel, reboot again, and enjoy. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major