Description of problem: Having problems with http kickstarting with --nobase Anaconda hangs on bootloader section... anaconda debugging shows anaconda going through the steps: blah blah /usr/lib/booty/bootloaderInfo.py File /usr/lib/python2.3/site-packages/rhpl/executil.py not found Shouldn't anaconda be installing the rhpl package regardless of package selection, just like it does the booty package, since it actually requires rhpl to be installed when writing the bootloader? Version-Release number of selected component (if applicable): RHEL4 U4 x86_64 How reproducible: Do an http kickstart with: %packages --nobase
This will be fixed in the next build of anaconda. If you require this fix in an updated version of RHEL, please talk to your support representative who will raise the issue through the proper channels. For now, it's simple enough for you to work around this problem by just adding rhpl to your packages section.
Sounds good. How is this fixed specifically? Is anaconda always going to install rhpl specificially, regardless of the contents of the %packages section?
We're keeping a list of packages that anaconda requires to have installed on the system for things that we do post-installation. These will be installed regardless of what you do in kickstart because they are selected after all the %packages section processing has occurred.
Perfect.... so far I've stumbled into these four being missing: rhpl system-config-mouse grub authconfig Thanks!