Bug 59443 - Kickstart vis nfs fails if your boot image is 'ks'
Summary: Kickstart vis nfs fails if your boot image is 'ks'
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-02-08 00:17 UTC by Mike Ireton
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-02-11 17:02:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mike Ireton 2002-02-08 00:17:59 UTC
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:

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

label ks
  kernel vmlinuz
  append initrd=initrd.img console=ttyS0,9600 console=tty0 devfs=nomount network
ksdevice=eth0 ks=nfs: 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.

Comment 1 Jeremy Katz 2002-02-11 17:02:26 UTC
A label 'ks' already exists by default in the syslinux.cfg; are you replacing
this section or just adding another one?  syslinux may well get confused by two
stanzas of the same name.

Comment 2 Jeremy Katz 2002-02-11 17:23:07 UTC
Email from the user --

        Hmm, now that I've looked again, I see there are two ks stanzas
on my test floppy. User misconfliguration, sorry.

Note You need to log in before you can comment on or make changes to this bug.