From owner-freebsd-questions  Sat Jan 11 14:00:45 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA08572
          for questions-outgoing; Sat, 11 Jan 1997 14:00:45 -0800 (PST)
Received: from netcom18.netcom.com (stanb@netcom18.netcom.com [192.100.81.131])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA08567
          for <freebsd-questions@freebsd.com>; Sat, 11 Jan 1997 14:00:43 -0800 (PST)
Received: (from stanb@localhost) by netcom18.netcom.com (8.6.13/Netcom)
	id RAA06308; Sat, 11 Jan 1997 17:00:42 -0500
From: stanb@netcom.com (Stan Brown)
Message-Id: <199701112200.RAA06308@netcom18.netcom.com>
Subject: Howto upgrade my 2.1.5 machine to 2.2 BETA ?
To: freebsd-questions@freebsd.com (Free BSD Questions list)
Date: Sat, 11 Jan 1997 17:00:41 -0500 (EST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

	I have a FreeBSD machine which is on my local network. It is connected
	via ppp to the local ISP, and provides the gateway to the world for the
	rest of my network. If it matters this is done using Charlie Mott's
	masquerading code.

	In order to use some new hardware on this machine, I need to upgrade it
	to 2.2. My question is how to do this with the minimal risk, and minimal
	downtime?

	I have never upgraded a FreeBSD machine before. I installed this one at
	2.1.5, and it quickly became my most flexible, trusted stable machine.
	Breaking it is a scary thought.

	Any advice is greatly appreciated.

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1996 Stan Brown.  Redistribution via the Microsoft Network is prohibited.