I found a different way around it. I had been putting in -firstboot* in my ks.cfg ... I changed that to -firstboot and -firstboot-tui as two separate entries. That seemed to work (though it might have been that in combination with my removal of @base-x) ...
Thanks everyone. Maarten Broekman Fidelity | Investment Management Technology Enterprise Platform Services Office: (617) 563-9756 Cell: (617) 590-8005 Skytel Pager PIN: 1062517 Email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Daniel Franklin Sent: Friday, July 18, 2008 2:12 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] Annoying firstboot rpms... On Fri, Jul 18, 2008 at 10:00 AM, Broekman, Maarten wrote: > If you have a completely scripted installation, is there any need for > the firstboot RPMs (firstboot and firstboot-tui)? Is there any reason > to keep them installed after the system is built and configured? > > I'm wondering because these two depend on a ton of other RPMs that we > don't use at all. However, when I try to remove them from my ks.cfg, > they get auto-included anyway. Yep, and again the secret is to use this in your kickstart to get yum and nothing else (add what you want such as openssh-server, pam_ldap, etc.): %packages --nobase yum-rhn-plugin _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
