[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Kickstart problems in FC2 [resolved]


 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

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= dns= ks=nfs: ksdevice=eth0

Very strange....


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= gateway= dns=
> ks=nfs: 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=
> Tries to boot and kernel panic ... DOH!!!
> <<<snip>>
> Kernel panic: Too many boot env vars at 'ip='
> 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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]