Subject: Re: Tool to update /etc (other than postinstall-fix)
To: Michael Graff <explorer@flame.org>
From: John R. Shannon <john@johnrshannon.com>
List: current-users
Date: 12/07/2003 02:17:43
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is something missing in etcupdate?
On Sunday 07 December 2003 02:07 am, Michael Graff wrote:
> I do something I suspect many others do as well. I build NetBSD on a
> machine, and rsync bits of the binary output around. This makes adding a=
nd
> upgrading machines trivial -- I only have to do the pkgsrc upgrade dance
> once, I can test before doing it, and I don't need to actually remove
> packages on production machines to upgrade them.
>
> It used to be that checking out src/etc was mostly sufficient to be able =
to
> upgrade /etc on the "client" machines, but now it seems I need a lot of
> src/sys as well. Also, some files in /etc are stored in usr.bin, or other
> directories.
>
> Are other people doing this sort of binary push, or am I unique? If I am,
> I can write something that can do the /etc upgrade, no matter how difficu=
lt
> it is becoming.
>
> Last time I brought this up (saying that 'postinstall-fix' should work
> without an entire source tree present by putting the needed bits in /usr/
> somewhere) I got flamed and told I was wrong to want this. I'm willing to
> change how I update my /etc, but checking out the entire source tree on 12
> machines is just silly.
>
> --Michael
=2D --=20
John R. Shannon
john@johnrshannon.com
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iEYEARECAAYFAj/S8DcACgkQOKbCxya4HYuARACdGLgTNLkOCYTbz51iQnTHIrMy
ADsAnifeqmlFY0RvEgiml1fMnoZgnrTr
=3DGxj3
=2D----END PGP SIGNATURE-----