I have a kickstart file that works fine under redhat 6.0.
I am trying it with 6.1 and there are no changes in the
format (that I can find documented) and there are several
things that don't work (as far as I can tell).
It doesn't look like the kickstart parser (in the .py file)
recognizes the static keyword - it always uses DHCP (and
Here's the line that works with rh6.0 kickstart
network --bootproto STATIC --ip 192.168.1.1 --netmask
Additionally I get an error on the follwoing line (the goal
of which is to say I don't have a mouse on this firewall box
I am building and please don't probe)
mouse --kickstart --noprobe none
For now, I will just keep using redhat 6.0 and applying the
Errata but if I am doing anything wrong, I'd appreciate
help. If these are real bugs then it would be great if they
could be fixed.
By the way, the "static" config dumped by "mkkickstart"
still has the incorrect "__static" keyword in it.
Have you tried "--bootproto static" (with lowercase letters)?
Works for me.
We are in the process of putting together a fix for this problem. We
should be releasing a fix the week of October 18th.
*** Bug 5952 has been marked as a duplicate of this bug. ***
I setup a boot floppy with a ks.cfg on it to test kickstart
installs. I typed "linux ks=floppy" when I booted the
floppy, and it booted the system, but it tried to get it's
IP address from DHCP instead of using what was specified in
the ks.cfg file. This works with RH 6.0.
University of California, Irvine
*** Bug 6340 has been marked as a duplicate of this bug. ***
Added a %pre scripting section
- Found the following bugs :
When assigning a static ip it still wants to grab a dhcp
The documentation needs to be updated within the manual,
there is no documentation on how to extend the kickstart
with python as said in the new features section.
This issue is resolved in the latest installer available in beta.