This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
From: neuroticimbecile <eric.rosel@q-linux.com> To: svlug@svlug.org Subject: Re: [svlug] Comments on commercial distros Date: Thu, 11 Oct 2001 00:26:52 +0800 On Wednesday 10 October 2001 23:54, you wrote: <snip> > > How do you distribute the changes to each machine? > > I have the same sorts of problems, and ~50 debian boxes at work to > keep those packages in sync on. I find it simplest to build ONE new > .deb, put it in my local apt archive, and run apt-get on each machine > ... as a matter of fact, I have a script > (http://people.debian.org/~lowe/aptwatcher) that runs apt nightly and > mails me if there are packages that need to be installed. In a large > environment, I'd go nuts without some automatic system to warn me when > new security packages have been released. > > I suppose I could accomplish the same thing on Redhat the way I did on > Solaris, with rdist or rsync, but that somehow seems less clean. hi there, i use the autoupdate package (http://freshmeat.net/projects/autoupdate/) to do just that on redhat boxes. i set up a local ftp server which regularly downloads redhat updates from mirrors via cron+mirror. the other redhat boxes on the local network then regularly run autoupdate, pointing to the local ftp server. autoupdate downloads the new rpms from the local ftp server and installs them. according to the docs which come with autoupdate, "it will try to handle dependencies and choose the right architecture (if more than one is available). Moreover, it will only download rpms for which an older version is present." you can even configure it to update the kernel and lilo.conf but that may be dangerous for some boxes. ===