kickstart not used in the boot process

Chris Lumens clumens at redhat.com
Fri Apr 13 14:16:07 UTC 2007


> I have created a ks.cfg with system-config-kickstart, and copied "my"
> packages in a temp directory
> I have copied it in the top level directory and in the isolinux directory
> I have chmod u+w isolinux/*
> 
> I have created a .iso file, according to
> http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/ch02s04.html
> Then burn it.
> I can read the CD fine.
> 
> When I boot, the ks.cfg file is ignored, as I am asked the language and all
> the usual questions.

If you have somehow managed to put the kickstart file in the wrong place
or anaconda otherwise cannot find it, you won't get any feedback.  It'll
happily try and fail to get the kickstart file, then keep going with an
interactive install.

So I don't know exactly what you're doing wrong, but be aware that
you're not going to get much help from anaconda on this.  This is fixed
in at least Fedora 7, possibly also in RHEL5.  I can't remember exactly.

- Chris




More information about the Kickstart-list mailing list