From owner-freebsd-current Wed Mar 18 19:28:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00867 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:28:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00852 for ; Wed, 18 Mar 1998 19:28:37 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id VAA15764; Wed, 18 Mar 1998 21:28:19 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35106C23.64774CD9@dsto.defence.gov.au> References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 18 Mar 1998 21:24:09 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: Disk munging problem with current solved Cc: joelh@gnu.org, c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:51 PM -0600 3/18/98, Matthew Thyer wrote: >Alas there is no synchronisation between CTM and cvs. > >Theoretically if you cvsupped at the same time as the person >who makes the CTM deltas and you created the .ctm_status >file yourself with the right number in it then you'd be right. > >However if you cvsup 1 minute later a couple of files somewhere >in the tree may have been changed and then future CTM deltas >would fail to apply. > >So no, you cannot use both CVS and CTM. I presume you mean CVSup. The CVS tree is certainly available by CTM. > >Use one or the other but not both. > This is NOT TRUE. If you use CVSup from ctm.freebsd.org, there is a direct correspondence because THAT distribution point is updated only by CTM. Except for the short "race" condition while updates are calculated and applied, it matches the latest CTM distribution of . This tree is also the tree from which the src trees are extracted to produce the other CTM distributions. The .ctm_status file is not present because that file for (and and ) are not distributed in the CVS tree. To resync , CVSup from ctm.freebsd.org is fine. To sync to the derived distributions is a little harder. By the present schedule, the cvs tree is updated every 8 hours. However, the extracted sources alternate and get updated only on a 16 hour cycle. This means that you would need to pick the appropriate time to do the (final) update in order to be back in sync. Richard Wackerbarth CTM Meister (retired) >Joel Ray Holveck wrote: >> >> > Note you will also need the last base delta for CURRENT >> > which you can download from: >> > ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-cur/ >> >> This reminds me: >> >> I noticed that it is possible to cvsup a current ctm tree from >> ctm.freebsd.org. I expect this to be either an alternative to using a >> base delta (for instance, now that you'd have to ftp nearly 100 >> deltas), or to allow you to resync a partially trashed source tree. >> However, this is missing .ctm-status, which would seem to be fairly >> important. >> >> (I'll also point out, with details that I didn't write down, that >> manually looking at deltas and figuring out where .ctm-status should >> be didn't work... I got a lot of missing stuff.) >> >> Am I doing something wrong here, or is that just something nobody's >> bothered with yet? >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message