I'm not sure why you think you need to make a new comps.xml for this... Try doing it this way.. Follow the howto on making a single CD install. Leave comps.xml file alone. In your %packages section, list the package groups and individual packages that you want, and do "-package" for those packages that belong to the groups that you don't want. Each type of install will have it's own set of packages, and you don't have to muck with comps.xlm. If you are installing RPMs that aren't part of the original distro, just do that in %post. James James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 anaconda-devel-list-bounces@xxxxxxxxxx wrote on 05/24/2004 07:43:16 AM: > Is there a mechanism that would allow you to load a kickstart file based on > a comps.xml group selection? Or some other mechanism other than specifying > at the boot prompt? > > What I am doing is creating FC2 into a single CD format, starting with just > a minimal set of packages. Then, as I create different load types, I add > them to a new comps.xml file I am creating. Each comps.xml group I am > creating will require a different set of %post instructions in my kickstart > file. Therefore, it would be nice to say what kickstart file to use based on > the selected group. > > For example, I am working on 3 sets of loads right now: Core (+chkrootkit, > snort, and clamav), Log (core + syslog and snmp), Monitor (Core + NMIS, > Nagios, MySQL (for snort data)) > > Each setup also contains a seperate kickstart file that performs permissions > hardening, account creation, system configuration and other things. So far I > have a seperate build for each one in order to get it to automagically use > the ks.cfg file on install. What would be nice is to combine all these on > the same disc but into seperate comps.xml groups and tell it to use ks.core > ks.log or ks.monitor depending on the selected group. > > Thanks, > > Greg King > > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
