From owner-freebsd-stable  Mon Jul  1 15:18:11 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA21561
          for stable-outgoing; Mon, 1 Jul 1996 15:18:11 -0700 (PDT)
Received: from rocky.mt.sri.com ([206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA21541
          for <stable@freebsd.org>; Mon, 1 Jul 1996 15:18:06 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA12140; Mon, 1 Jul 1996 16:17:46 -0600 (MDT)
Date: Mon, 1 Jul 1996 16:17:46 -0600 (MDT)
Message-Id: <199607012217.QAA12140@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Cc: nate@mt.sri.com (Nate Williams), stable@freebsd.org
Subject: Re: Update 2.1-STABLE -> 2.1.5-RELEASE
In-Reply-To: <199607012215.PAA29225@GndRsh.aac.dev.com>
References: <199607011958.NAA11078@rocky.mt.sri.com>
	<199607012215.PAA29225@GndRsh.aac.dev.com>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > As I understand it, there *IS* an upgrade path from 2.1R.  Jordan would
> > know more.  However, the original poster asked for a CTM upgrade from
> > 2.1-STABLE -> 2.1.5, and there isn't any '2.1-STABLE' release to upgrade
> > from.  Also, creating a 'CTM' diff between 2.1R and 2.1.5 would be
> > *HUGE*, probably bigger than downloading the entire release, so if you
> > want the new sources you're more than welcome to download the entire new
> > release and do a 'make world' and then hand-upgrade the /etc files by
> > hand.  This is essentially what the 2.1R -> 2.1.5 'upgrade' would do
> > anyway.
> 
> cvs rdiff -u -rRELENG_2_1_0_RELEASE -rRELENG_2_1_0 src
> 
> GndRsh:rgrimes {215} ls -lag BIG.diff
> -rw-rw-r--  1 rgrimes  rgrimes  11171459 Jul  1 14:51 BIG.diff
> 
> GndRsh:rgrimes {218} df /usr/src
> Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> /dev/sd0g      158863   127050    19103    87%    /usr/src
> 
> 11MB vs ~127MB for a full src tree, both uncompressed, but compression
> should still keep the same 10:1 relative size difference.

This assumes that the diff takes into account all of the changes that
have been made.  Unfortunately, if you apply that diff to a virgin 2.1R
tree you won't get the same tree as a 2.1.5 tree due to
removal/additions and such.  The only *safe* way of doing this is to
start with a 2.1R CD and build a set of patches from it.  Unionfs would
be great for that. :)


Nate