Kickstart problems in FC2 [resolved]

[Robert Cavey]

Hmmm,

 As someone pointed out to me via direct re-ply -- <<<I believe the
maximum number of boot env vars is eight; look for MAX_INIT_ENVS (should
be in init/main.c) for the answer.

It certainly seems to me that eight would be insufficient for this
kind of thing, but it also doesn't look like you are using that many.
>>>

In fact I was using 6 and adding the 7th via boot option of "ks
ip=xxx.xxx.xxx"

Well .. my fix was to remove the gateway variable, now my line looks
like below which turns out to be 5 variables, hmmmmm.  Is the boot
process adding extra variables that are hidden to the eye somewhere?

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


Very strange....


Bob



On Wed, 2004-05-19 at 16:57, Robert Cavey wrote:
> 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