#185 wrong line in the default kickstart install setup
Closed: Fixed Opened by anonymous.

when set the:
"set installer to boot with kickstart by default"
the result iso image for cd kickstart append should have to be:
"append ks=cdrom:/ks.cfg initrd=initrd.img"
while it's in the iso:
"append ks initrd=initrd.img"
imho it'd be easy to fix for those where it's:-)

on the other hand (may be related) the isolinux/isolinux.cfg has duplicate entires (the first one should have to be deleted) i.e. even if i set to "include kickstart file on installation media" and "set installer to boot with kickstart by default" it's not working:

default linux
prompt 1
timeout 600
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
label linux
kernel vmlinuz
append initrd=initrd.img
label text
kernel vmlinuz
append initrd=initrd.img text
label ks
kernel vmlinuz
append ks initrd=initrd.img
label local
localboot 1
label memtest86
kernel memtest
append -

default ks
prompt 1
timeout 600
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
label linux
kernel vmlinuz
append initrd=initrd.img
label text
kernel vmlinuz
append initrd=initrd.img text
label ks
kernel vmlinuz
append ks initrd=initrd.img
label local
localboot 1
label memtest86
kernel memtest
append -



and if the solution for the append problem is a one liner i'd like to know it before the next release:-)

and if the solution for the append problem is a one liner i'd like to know it before the next release:-)

The duplicate entries in isolinux.cfg have been resolved.
The 'ks' parameter should make anaconda search for the kickstart file as being named 'ks.cfg', so we're gonna put that to the test and if it fails append ks=cdrom:/ks.cfg.

The duplicate entries in isolinux.cfg have been resolved.
The 'ks' parameter should make anaconda search for the kickstart file as being named 'ks.cfg', so we're gonna put that to the test and if it fails append ks=cdrom:/ks.cfg.

yes that's true, but it seems to not working. have you try it? the ks.cfg file is in the root and when i boot from the cd i get an error message to give the right kickstart location the window contains:
ks
when i edit it to
ks=cdrom:/ks.cfg
then it start to working.

yes that's true, but it seems to not working. have you try it? the ks.cfg file is in the root and when i boot from the cd i get an error message to give the right kickstart location the window contains:
ks
when i edit it to
ks=cdrom:/ks.cfg
then it start to working.

OK, since we set the ks.cfg static anyway, I suppose there's no problem in linking it statically either. I've barely tested this because when I did use this, I forgot to include the kickstart on the media... :/

OK, since we set the ks.cfg static anyway, I suppose there's no problem in linking it statically either. I've barely tested this because when I did use this, I forgot to include the kickstart on the media... :/

please let me know if you made any changes to the source to do this (the changeset is would be the best) and i'll happy to test it:-)

please let me know if you made any changes to the source to do this (the changeset is would be the best) and i'll happy to test it:-)

Fixed in the latest code, haven't tested it though

Fixed in the latest code, haven't tested it though

is there is a new rpm build for f7 i'd be happy to test it:-)

is there is a new rpm build for f7 i'd be happy to test it:-)

Seems I'm gonna be testing it too ;-) I can build you an RPM but you'll have to wait until I fix some other issues that I'm working on as well.

Seems I'm gonna be testing it too ;-) I can build you an RPM but you'll have to wait until I fix some other issues that I'm working on as well.

Metadata Update from @anonymous:
- Issue set to the milestone: 2.0.4 Release

Metadata