From owner-freebsd-questions  Fri Feb 21 23:49:02 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA27515
          for questions-outgoing; Fri, 21 Feb 1997 23:49:02 -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 XAA27507
          for <questions@FreeBSD.org>; Fri, 21 Feb 1997 23:48:58 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id XAA00868; Fri, 21 Feb 1997 23:48:31 -0800 (PST)
Date: Fri, 21 Feb 1997 23:48:31 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Riss <riss@Mcs.Net>
cc: questions@FreeBSD.org
Subject: Re: Upgrade
In-Reply-To: <199702211721.LAA08961@Mars.mcs.net>
Message-ID: <Pine.BSI.3.94.970221234820.421N-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 21 Feb 1997, Riss wrote:

> Dumb question I know... but what is the most painless way to upgrade
> a currently running 2.1.5 system to 2.1.7 ? I mean downloading or
> gettign the cd is no problem. But I am unsure exactly what to do
> and what files to replace or if anythign needs to be recompiled.
> Can you point me in the right direction ?

Sure can.


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