Date: Sat, 21 Mar 1998 07:56:58 -0800 From: John Polstra <jdp@polstra.com> To: current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) Message-ID: <199803211556.HAA18058@austin.polstra.com> In-Reply-To: <l03130308b13643d4b470@[208.2.87.4]> References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> <l03130308b13643d4b470@[208.2.87.4]>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <l03130308b13643d4b470@[208.2.87.4]>, Richard Wackerbarth <rkw@dataplex.net> wrote: > At 9:09 PM -0600 3/18/98, Matthew Thyer wrote: > >I dont know about this... hopefully someone else can comment on it. > > > >It would be good to be able to cvsup for a latest VM fix and then > >to be able to re-synchronize with CTM later. > > The ability to do this is somewhat limited by the problems > associated in jumping from one CVSup server to another. I want to make sure nobody is misled by the above statement. There is _no_ inherent problem with jumping from one CVSup server to another. It works just fine as long as you're not trying to mix CVSup and CTM updates. What Richard was referring to (I guess) is that the various CVSup mirrors make no attempt to stay in lock-step with each other, or with the CTM deltas. So what you find on one CVSup mirror might be a little more or a little less up to date than what you find on a different mirror. This doesn't bother CVSup in the least. Also, the variation between servers is quite small in practice, since most of the mirrors update their files from the master site hourly. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803211556.HAA18058>