no cvsup(8)?!

[Garance A Drosihn]

At 12:49 AM -0400 10/18/05, Ben Rosengart wrote:
>On Sun, Oct 16, 2005, Peter Grehan wrote:
>  >
>>   In the meantime, you might want to give csup a try:
>>
>>    http://mu.org/~mux/csup.html
>>
>>   It's been reported to work on FreeBSD/ppc.
>
>This is great, though it's rather brittle -- I sometimes have to run
>it a few times to get through an entire update -- switching servers
>each time so as not to hit the access limits.  I see from the docs
>that the developer is aware of these issues.  Much better than
>nothing.  :-)  Are you using this, or cvs, or what?

In my case, I have several machines running freebsd.  Due to that, it
is worthwhile for me to set up one of those machines (an Athlon) as a
cvsup-mirror.  All my other freebsd machines then connect to my own
local cvsup server, so I don't have to worry about hitting access
limits.

For my PPC machine, the second trick I do is that I run cvsup the CVS
repository into a separate directory on one of my Athlon machines.  I
then nfs-export that directory to the powerPC machine, and the powerPC
machine does a 'cvs checkout' from the nfs-mounted directory.  Thus the
powerPC machine does not have to run cvsup.  It sounds like a lot of
work to set up, but actually it isn't as hard as it sounds.  I also
cvsup the ports collection into a separate directory on my athlon, and
nfs-export that to the powerPC machine.

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu