From owner-freebsd-stable  Sat Aug 16 12:31:33 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA07062
          for stable-outgoing; Sat, 16 Aug 1997 12:31:33 -0700 (PDT)
Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07052
          for <freebsd-stable@freebsd.org>; Sat, 16 Aug 1997 12:31:28 -0700 (PDT)
Received: from localhost (jamil@localhost)
	by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id MAA04979;
	Sat, 16 Aug 1997 12:30:51 -0700 (PDT)
Date: Sat, 16 Aug 1997 12:30:51 -0700 (PDT)
From: "Jamil J. Weatherbee" <jamil@counterintelligence.ml.org>
To: David Greenman <dg@root.com>
cc: freebsd-stable@freebsd.org
Subject: FreeBSD 2.2.5 Release
In-Reply-To: <199708161207.FAA26252@implode.root.com>
Message-ID: <Pine.BSF.3.96.970816122718.888A-100000@counterintelligence.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


If you are going from 2.2.2 to 2.2.5 CD's will it be possible to do an
upgrade easily or am I better off leaving any critical servers running the
ports/stand utils from 2.2.2 and just keeping up with the cvsups on the
stable tree?

Yes, I did take a look at the sysinstall upgrade function but that seems
like you might be better off just leaving it alone.