From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.17 i686)

Description of problem:
If the installation is started via floppy, using a section label of 'ks'
(presumably, a user added section to the distributed boot image that means to
boot via kickstart with user supplied options...), anaconda will fail to locate
the correct ks.cfg file, even tho it's correctly appended to the kernel command
line paramaters. Renaming the boot section to something other than 'ks' corrects
the problem.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a boot floppy using images/bootnet.img from the redhat cdrom.
2. Modify the file syslinux.cfg so that it has a new section named 'ks'. For
example:

label ks
  kernel vmlinuz
  append initrd=initrd.img console=ttyS0,9600 console=tty0 devfs=nomount network
ksdevice=eth0 ks=nfs:192.168.1.254:/opt/redhat/ks-default.cfg text

3. Boot from this floppy and select this image to boot.

	
	

Actual Results:  
	Assuming you had a dhcp server and an nfs server as specfied above in the
command line, the system would fail to locate 'ks-default.cfg' on the nfs
server. Instead of using nfs to mount /opt/redhat, grab the specfied file, then
do an install from /opt/redhat, the system instead tries to mount /kickstart
from the dhcp server.


Additional info:


Renaming the section from 'ks' to anything else, immediately fixes the problem.