Patch fixing a problem with --kickstart-include
 

By naming the kickstart file as ks.cfg, anaconda would _always_ take
it, regardless of kernel boot options. This is not what was expected -
it is safer to give it a different name, and then use the boot menu
item to select it.

The patch is on top if F-9 .

cheers,



m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

Patch fixing a problem with --kickstart-include
 

Martin Langhoff wrote:

By naming the kickstart file as ks.cfg, anaconda would _always_ take
it, regardless of kernel boot options. This is not what was expected -
it is safer to give it a different name, and then use the boot menu
item to select it.



So what you're saying is that anaconda picks up the kickstart file and
runs away with it, even when it has not been told it should do so? It
probably shouldn't do that... but I'll have to check with the anaconda
guys to see if it's maybe an intended change.


Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list