Kickstart problems in FC2

Robert Cavey rcavey at g0mos16.gsfcmo.ecs.nasa.gov
Wed May 19 20:57:31 UTC 2004


Having problems building my kickstart disk in FC2. Used this exact same
method with RH90 and was flawless.

The scoop:
Basically, I unpack the boot.iso from the images directory and modify
the isolinux.cfg and change ks label to the following:

<<SNIP>>
label ks
  kernel vmlinuz
  append netmask=255.0.0.0 gateway=10.1.198.1 dns=10.1.198.31
ks=nfs:10.1.198.138:/data1/kickit/fc2ks.cfg ksdevice=eth0
initrd=initrd.img
<<SNIP>>

I then run mkisofs to rebuild to a .iso and burn to CD, boots up OK, at
the boot prompt:

boot: ks ip=10.1.198.105

Tries to boot and kernel panic ... DOH!!!

<<<snip>>
Kernel panic: Too many boot env vars at 'ip=10.1.198.105'
In idle task - Not syncing
<<<snip>>>


If I just type "ks" anaconda tries to dhcp the nic card ... don't want
that.


Anyone know of a limit to the number of parameters or has the process
changed with the 2.6 kernel?


Thanks,
Bob






More information about the test mailing list