Venkatraju
2008-Sep-24 15:14 UTC
[CentOS] CentOS 5.2 kickstart install with latest updates
Hi, The CentOS 5.2 release notes contain this warning: "A kickstart installation that attempts to use the *repo* directive (where that *repo* points to an updates repository) may fail to properly install." This is exactly the method that I had been using with CentOS 5.1 :-) What is the right way to achieve this now? Is adding a repository in the %post section of the kickstart file and running "yum update" safe? Anyone run into problems with this? Thanks in advance, Venkat -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080924/c5afa417/attachment-0001.html>
Steve Thompson
2008-Sep-24 15:32 UTC
[CentOS] CentOS 5.2 kickstart install with latest updates
On Wed, 24 Sep 2008, Venkatraju wrote:> Is adding a repository in the %post section of the kickstart file and > running "yum update" safe? Anyone run into problems with this?I am using exactly this method with CentOS 5.2. So far only about 20 installations, but I have not had a problem with any of them. Steve
Matthew Kent
2008-Sep-24 15:56 UTC
[CentOS] CentOS 5.2 kickstart install with latest updates
On Wed, 2008-09-24 at 20:44 +0530, Venkatraju wrote:> This is exactly the method that I had been using with CentOS 5.1 :-) > What is the right way to achieve this now? Is adding a repository in > the %post section of the kickstart file and running "yum update" safe? > Anyone run into problems with this?No issues with it so far in my many kickstart installs. It's actually nicer since I can use yum-priorities to get exactly what I need installed. [Worth noting that priorities have been added to the repo directive in anaconda in later versions] -- Matthew Kent \ SA \ bravenet.com
Karanbir Singh
2008-Sep-24 16:23 UTC
[CentOS] CentOS 5.2 kickstart install with latest updates
Venkatraju wrote:> The CentOS 5.2 release notes contain this warning: > "A kickstart installation that attempts to use the *repo* directive > (where that *repo* points to an updates repository) may fail to properly > install."In some tests we did at 5.2 install time we found that the updates failed to register completely, but lots of people seem to report no such issues in the wild. So I guess if it works for you, thats fine. Go for it. - KB