Okay that makes sense. I don't really do updates so I'll let folks who use that comment on this.
If this currently is not supported, it wouldn't be a bad feature to include. Thanks, Bernard > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Ben Hartshorne > Sent: Monday, January 09, 2006 18:22 > To: [email protected] > Subject: Re: [Sisuite-users] overrides and timing issues > > On Mon, Jan 09, 2006 at 06:17:21PM -0800, Bernard Li wrote: > > If you're updating, why wouldn't you just put the override > files as the > > "stock" files and forget about the overrides altogether? > > they don't go in the base image (do I mean the same thing by 'base > image' as you do by 'stock'?) because they are different for the > different servers. > > Let's say you have half of your servers that need mod_perl, but you > don't want it on the other half (for speed). The particular features > are irrelevant, the idea is that you have a different > configuration (in > some aspect) between two servers, but 90% of the stuff is the same. > > If you want to upgrade glibc, you do it in the base image, > and that gets > propogated to everywhere via the nightly update. > > If you want to upgrade mod_perl, you do it in the overrides directory, > and only the appropriate hosts are affected when the nightly update > comes around. > > Do overrides not work for updates, but only installs? > > -ben > > -- > Ben Hartshorne > email: [EMAIL PROTECTED] > http://ben.hartshorne.net > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
