From owner-freebsd-questions  Mon Mar  3 23:26:42 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA02731
          for questions-outgoing; Mon, 3 Mar 1997 23:26:42 -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 XAA02725
          for <questions@freebsd.org>; Mon, 3 Mar 1997 23:26:38 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id XAA21357; Mon, 3 Mar 1997 23:26:25 -0800 (PST)
Date: Mon, 3 Mar 1997 23:26:25 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Mike Tancsa <mike@sentex.net>
cc: questions@freebsd.org
Subject: Re: is -O2 -m486 -pipe safe ?
In-Reply-To: <3.0.1.32.19970303100950.00944180@sentex.net>
Message-ID: <Pine.BSI.3.94.970303232529.21192M-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 Mon, 3 Mar 1997, Mike Tancsa wrote:

> 
> I am going to upgrade our 2.1.5 FreeBSD news machine to 2.1.7 by
> downloading the new src tree and doing a make world with those options....
> Is it safe to do, or should I stick with with regular -O for optimzations...

Why not just run the 'upgrade' procedure from sysinstall?  Or is there a
directive to use ``make all install'' and not 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