On 6/7/07, Ernest <kong_an563@xxxxxxxxx> wrote:
RE: Date: Thu, 7 Jun 2007 23:14:46 +0200 From: Nigel Henry <cave.dnb@xxxxxxxxxx> Subject: Re: No kernel removal by yum I have learned how to work around the problem of yum deleting the downloaded packages when it has finished an update. I also have dialup, and have learned that one can interrupt the dialup session, shutdown the computer, and the package files successfully downloaded will remain in /var/cache/yum/../packages. You can restart the yum upgrade at a later time, and those packages already in place, locally will not be downloaded a second time. As the days go by, the list of packages to download will shrink, and eventually you'll have them all. Then... when yum begins to digest all of those packages, open a second console, and copy all of the package files from where ever yum has cached them, to some other directory. I send them to a NFS server on my LAN, before yum has finished the upgrade, and before yum deletes the cache. Then... on any other machine you wish to upgrade, you can use "yum localinstall /path/to/NFS/or other/*.rpm". Yum will then digest the saved copies of the downloaded packages, resolve dependencies, download any other packages needed, and preform the upgrade. This, of course, presumes that the other machines you are upgrading have a path to your saved packages, and an internet connection. I'm looking at 1.1GB download, to upgrade one desktop from FC6 to FC7.
Why are you jumping through hoops to keep packages in the cache from being deleted? Use a text editor, edit /etc/yum.conf, and change "keepcache=0" to "keepcache=1".
