Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Aug 2002 12:54:52 -0400
From:      Barney Wolff <barney@tp.databus.com>
To:        Matthias Trevarthan <trevarthan@wingnet.net>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: setting up a CVSup repository
Message-ID:  <20020814165452.GA30493@tp.databus.com>
In-Reply-To: <200208141032.04447.trevarthan@wingnet.net>
References:  <200208140919.35737.trevarthan@wingnet.net> <20020814140526.GA29078@tp.databus.com> <200208141032.04447.trevarthan@wingnet.net>

next in thread | previous in thread | raw e-mail | index | archive | help
cvs can do checkouts from a remote archive - see the manpage or other
docs.  The advantage of running that way is you don't need to learn
about the cvsup daemon and the clients can look at any version of
any file, whenever they want to, without having to cvsup a whole
collection.  cvsup's real advantage in efficiency counts for a lot
over the Internet, not so much over a LAN.

As cvs can use ssh for its remote operations, you don't have to be
worried about NFS (or rsh).

But really, you should not be keeping your cvs archive, or cvsup
mirror, outside the firewall.  A compromise of the machine that
holds your organization's OS sources would be an utter disaster
that you might not detect for a long time, if ever - or you might
hear about it first in the newspaper.

However, if your organization has multiple levels of firewalls with
internal areas of differing security context, cvsup may be an easier
sell to the firewall gods than ssh or nfs.

Re ports, remember that what cvsup (or cvs) gives you is the port
skeleton, not the distribution files.  So you should think about
setting up a way for those to be downloaded from their often-overloaded
sources just once.  Running an http/ftp proxy would seem wise, if
you really want multiple systems building ports.

On Wed, Aug 14, 2002 at 10:32:04AM -0400, Matthias Trevarthan wrote:
> 
> > 1.  As you asked, set up your own cvsup mirror.  It seems to me that
> > this is the way to go only if the systems that will be using it are
> > not under your direct supervision.
> >
> > 2.  Do cvsup of the cvs archive on one machine, then have others do
> > their own remote CVS checkouts from the archive on that.  This is simpler
> > in some ways on the server, and really no harder on the clients.  It
> > allows you to build current and stable and cpu flavors, as you wish.
> >
> 
> I'm a little confused about the differences between one and two. Could you 
> elaborate? 

-- 
Barney Wolff
I'm available by contract or FT:  http://www.databus.com/bwresume.pdf

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020814165452.GA30493>