[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-misc
Subject:    Re: Creating update tarballs
From:       Gerardo Santana Gomez Garrido <santana () openbsd ! org ! mx>
Date:       2002-08-21 23:46:03
[Download RAW message or body]

I'm assuming you are updating to -stable.

Why do you compile the whole system?
Compile just the programs affected and pack only those that change. Then
apply them to the rest of your servers.

That's what binary patches do.

On Wed, Aug 21, 2002 at 05:59:13PM -0400, Rod Dorman wrote:
> I've read & tried the procedure described on the 'release' man page
> to create a set of tarballs that I used to update another machine.
> 
> Works fine except it spent a lot of time compiling which was what I
> was trying to avoid in the first place.
> 
> In looking thru /usr/src/etc/Makefile I noticed it used
> /usr/src/distrib/sets/maketars to create the tarballs from DESTDIR
> so I tried the following:
> 
>     cd /usr/src/distrib/sets
>     setenv DESTDIR /
>     setenv RELEASEDIR /tmp/tars
>     cp /bsd /tmp/tars
>     sh maketars 31
> 
> and other than one complaint about "Unable to access ./var/tmp/vi.recover"
> it appeared to do what I wanted, i.e. collect the patched -stable system
> into tarballs useable for updating another machine.
> 
> They're both i386 boxes using the GENERIC config so there shouldn't
> be any issues in that respect.
> 
> Is this an acceptable procedure for updating slower machines or is
> there something I'm missing?
> 
> -- 
> rodd@polylogics.com
>            "Hangers on though you be friends be more humble
>            when asking for seconds."
>               Katsuhito Masaki (Grandfather); Tenchi Muyo Episode 7

-- 
Gerardo Santana Gómez Garrido
http://www.openbsd.org.mx/~santana/
OpenBSD México

[prev in list] [next in list] [prev in thread] [next in thread]