Kickstart config automation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a variety of user types, hardware types, and RedHat distributions that I'm responsible for and I need to add some more automation into my Kickstarts to make them "smarter" and to perhaps enable users to load there own machines.  I currently point to one of several kickstart configuration files on an NFS server, but maintaining many kickstart files is getting troublesome.

 

For example, if I need to start including a new package in new installs, I have to edit all of the kickstart files and add the package to the %package section.  I tried using an %include statement and point to files that contained my base package lists, but I didn't get it right.  Anaconda couldn't see the files I was referencing.  I tried mounting the remote filesystems in the %pre section, but it still didn't see them.  Anyway, that's just a example of how stupidly I'm doing things now.

 

I was intrigued by the idea that was brought up recently about using a CGI script to determine options.  How would you run the CGI?  Would you just do an HTTP GET from the %pre section and put the output in /tmp, then %include it?  How would you pass parameters to the CGI (could you pass them in at the "boot" prompt)?

 

Thanks in advance,

Nick

 

_________________________________

Nick White

Systems Engineer

Landmark Graphics Corp.

 


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux