I have not looked at Yam, I'll at it to my todo list. Let me explain my problem again... I have CDs of CentOS-3.3 x86_64 (which I downloaded a while back to test on an Athlon64. A lack of video drivers meant that the 64 bit version was no good so the test was abandoned.) Now I have received an EM64T server (DL380 G4) and I want to test CentOS-3 x86_64 that, so I installed from the 3.3 CDs. Now I can point my yum config at the 3 updates directory (which I have mirrored locally) but there are required patches which are not in there! I know that the patches are in 3.4 base but I don't want to download that. All I want is the changes from 3.3 to 3.4. If these were in the 3 updates then I would be fine.... but they are not :( So now I have to download 3.4 and set it up on my local mirror, even though I have most of the files already on my 3.3 CDs and on my mirror already. Worst of all.... when 3.5 comes out I have to do it all again. And again for 3.6 and 3.7 etc. until 3.28 I think there is a better way. Make a CentOS-3 updates directory, and every update since CentOS-3 was released goes in there. Keep the latest patch and the previous version and move the older ones into an historical archive (or delete them). This is what every other distro I have used does (RH6.2, RH7.2, RHEL2*, RHEL3*, CentOS-2). * patches were download manually and not with rsync. Once set up, there is no need to alter the yum config ever again. John. Dag Wieers wrote: > On Tue, 19 Apr 2005, John Newbigin wrote: > > >>Lance Davis wrote: >> >> >>>On Tue, 19 Apr 2005, John Newbigin wrote: >> >>If I had 3.4 media I could just install off that. I am looking at a local >>mirror setup which does not require me to download new CDs every 3 months. > > > John, I'd like to add a feature to Yam that allows to generate new > metadata for anaconda based on the currently available updates. This would > allow to add 3rd party packages and custom packages to a network-based > installation without requiring a new set of ISOs (just the downloaded > updates). > > So for kickstart installations you wouldn't need to install additional > stuff from the %post section or after the first reboot. > > The only reason to get newer ISOs in that case would be if you require a > newer anaconda/kernel for the installation itself. > > Insights, feedback or patches are welcomed :) > > -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- > [all I want is a warm bed and a kind word and unlimited power] > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > > -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin