--- Ingo Schwarze <[EMAIL PROTECTED]> wrote:
> Hi Juan,
>
> Juan Miscaro wrote on Sun, Nov 25, 2007 at 10:31:30AM -0500:
>
> > I have a 4.2 master system which I intend to use
> > to quickly install new systems.
>
> This does make sense.
>
> You do not tell us whether you are using 4.2-stable or 4.2-current.
> Both are good choices; in any case, make sure you know which one
> you are using, and stick to it.
>
> Also read: http://www.openbsd.org/faq/faq5.html#Flavors
>
> > I have rebuilt the master system with updated sources;
> > made the release sets;
>
> So far, this is standard practice for both -stable and -current.
>
> > and made tarballs of /usr/src.
>
> What are you going to with a src tarball?
> I suspect you won't need that kind of beast at all.
> Besides, why are you using the plural "tarball*s*"?
I made a tarball of /usr/src and of /usr/ports
> > 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.
>
> Here i'm losing track of what you are doing.
> I suppose you are referring to your src tarball(s)?
> I suspect you won't need source code on the client machines.
>
> The standard way to handle upgrades is to update the src
> on the master only, to build new release sets on the master,
> and to use the official upgrade process to install these
> new release sets on the clients. That way, none of the
> clients will ever need source code.
I'm embarrassed to say that I was intending to build my client systems
locally. The ports tree can be useful though.
> > 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.
>
> Unless you tell us what you mean by "test update" (cvs update?
> which server? which command, exactly?) even guessing is difficult.
>
> In case you are talking about
> cd /usr/src; cvs up -dP
> this will take some time, even with a quick network link, using
> a public mirror in your own country and without many changes.
> For the above command, five minutes would seem normal even
> using a 100 Mbit/s internet connection.
But why should there be such a change if I just finished updating those
same sources on the master?
> But probably this whole discussion is moot.
> I fail to see the point in copying /usr/src to several machines.
> If you just want to be able to read the source from all machines,
> you might want to use NFS, possibly in read-only mode.
> If you really need to copy the source to many machines,
> you should probably set up your own internal cvs mirror -
> but what for?
Actually, the master is inside my company network whereas the clients
are remote systems (in the field).
[snip]
Thanks for the advice.
// juan
Looking for a X-Mas gift? Everybody needs a Flickr Pro Account.
http://www.flickr.com/gift/
