Red Hat Bugzilla – Bug 52645
mkkickstart improperly set lilo and xconfig
Last modified: 2007-04-18 12:36:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.61 [en] (Win95; U)
Description of problem:
When I ran mkkickstart, several commands were set wrong. For the xconfig line the --server value contained a valiant effort to find the X
driver, though not the driver itself. It read:
xconfig --server "/etc/X11/X: symbolic link to ../../usr/X11R6/bin/XFree86" ...
The other error I found in the output file from mkkickstart is that the lilo command was used instead of bootloader (which should load the
GRUB boot loader by default).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mkkickstart > /tmp/ks.cfg
Actual Results: The ks.cfg file was created with the improper settings.
Expected Results: Should have indicated the proper X server and bootloader.
I made those changes and a few others to suit my system. Apparently I did not get the partitioning commands right because when I ran "linux
ks=floppy" to do the kickstart it blew away my MBR and installation failed. Bummer.
*** This bug has been marked as a duplicate of 53073 ***