From owner-ctm-announce Tue Oct 21 22:03:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA05824 for ctm-announce-outgoing; Tue, 21 Oct 1997 22:03:52 -0700 (PDT) (envelope-from owner-freebsd-announce) Received: from set.spradley.dyn.ml.org (fcn104-99.tmi.net [207.170.104.99]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA05816; Tue, 21 Oct 1997 22:03:40 -0700 (PDT) (envelope-from tsprad@spradley.dyn.ml.org) Received: from set.spradley.dyn.ml.org (tsprad@localhost.sands.com [127.0.0.1]) by set.spradley.dyn.ml.org (8.8.5/8.8.5) with ESMTP id AAA21167; Wed, 22 Oct 1997 00:18:54 -0500 (CDT) Message-Id: <199710220518.AAA21167@set.spradley.dyn.ml.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Wackerbarth cc: ctm-announce@freebsd.org Subject: Re: Notice of Temporary Suspension of Updates In-reply-to: Your message of "Tue, 21 Oct 1997 20:21:31 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Oct 1997 00:18:53 -0500 From: Ted Spradley Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have chosen to do this because the advantage of being able to use the > 2.2.5 CD for a baseline > outweighs the disadvantage caused by the slight delay. > > I encourage everyone to obtain the 2.2.5 Release CD. Those using CTM or > CVSUP to update can > significantly reduce the huge file transfer involved in starting the update > process. Is this something new, or was this the case with the 2.2.2 CD as well? I have the 2.2.2 CD and all the CTM feeds, but when I tried to ftp the 36 Mbyte src-2.2.0400xEmpty.gz it died after about 32 Mbytes. Is there something on the 2.2.2 CD that I can apply the CTM updates to in order to get 2.2.5 before the new CD arrives in the mail? When I tried to apply the updates directly to /usr/src from the CD ctm refused because there was no .ctm_status.