On Sun, Nov 25, 2007 at 03:12:09PM -0500, Juan Miscaro wrote:
> --- Joachim Schipper <[EMAIL PROTECTED]> wrote:
>
> > On Sun, Nov 25, 2007 at 10:31:30AM -0500, Juan Miscaro wrote:
> > > I have a 4.2 master system which I intend to use to quickly install
> > new
> > > systems. I have rebuilt the master system with updated sources;
> > made
> > > the release sets; and made tarballs of /usr/src. I installed a
> > client
> > > system with the sets over ftp. All is well.
> > >
> > > I want to eventually be able to update the client source code once
> > in
> > > the field so I unpacked the master tarballs. The trouble is that
> > when
> > > I performed a test update of this code there was a immense amount
> > of
> > > downloading taking place. This should not have been the case.
> > >
> > > Given that I may have committed a mistake with the creation of the
> > > tarball is my method sound? It seems like a typical operation.
> >
> > What's an 'update' in this context? And exactly what was doing the
> > downloading?
>
>
> I use cvsup to update my sources (to STABLE):
>
> *default release=cvs
> *default tag=OPENBSD_4_2
> *default host=cvsup.no.openbsd.org
> *default base=/var/cvsup
> *default prefix=/usr
> *default delete use-rel-suffix
> *default compress
And was it downloading more files than on your 'master' server? -stable
doesn't receive that many updates, but that can still be quite a few
files.
Joachim
--
TFMotD: netstart (8) - command scripts for network startup
