On Thu, 19 Jun 2003, Tom Duerbusch wrote: > Bring it back to my question from a few weeks back...that was, how to > keep a Penguin farm, under the same set of updates: > > When I did the YOU updates to one of the images a few weeks ago, I saved > the RPMs instead of deleting them. So, it seems to me that if I mounted > that disk in r/o mode for other images, I should be able to run rpm from > that directory, and have that image brought up to the same maintenance > level as the base image...right?
Maybe. IF you have the same packages on both systems, then probably. I'd not be at all surprised if YOU has its own ideas about what's going on. What I suggest is this: At some point between your domain (stuff you control) and The Rest of the World, create a firewall rule that says http traffic to Suse (or everywhere if you like, I do) goes to squid.example.com, port 3128. Run Squid on that box, configured to cache everything, and for transparent proxy. First time you download (assuming YOU uses http) example.2.0-next.s390.rpm it gets cached when it's pulled from SuSE. Second and subsequent times, Squid serves it up instead of downloading it. Do check it acually works: the SuSE folk _could_ be bloody-minded enough to defeat this, but probably not. It works a treat for Debian. I installed it on a Powermac yesterday. In fact, I did install from CD, but if I'd used the net, then the install I plan on for later today would come off my LAN at 10 Mbits/sec instead of an external server at 512 bits/sec. -- Cheers John. Join the "Linux Support by Small Businesses" list at http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
