And this would work MUCH better in a environment with change control active. I can't use yum on production machines because it 'might' pull in something that I do not have permission to upgrade. Better to download first, verify it is correct, then install the specific packages with rpm directly under the control of an enterprise scheduling regime (we use Control-M and Tivoli). If yum found other dependencies than expected, then the change fails and you try again later. 'Enterprise' is so much fun.... On Thu, 9 Oct 2003, Steve Traylen wrote: > > yum -d update > > which would just download the packages required for an update. > and a > > yum clean oldpackages > > that would delete rpms from the cache that were no longer needed for > an update. > > With this I have on the local filesystem system all the packages I need > to run the actuall update which will now be a very quick and uniform > operation. > > Steve ------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim@xxxxxxxxxxxxx http://www.rossberry.com
