Mike,
There is no need to give the kickstart file a specific name, as you start
the installation using the name, anything will do.
It looks to me that your slash is out of place ( ks=cdrom:/ks.cfg should be
ks=cdrom:ks.cfg )
keep in mind that on your cdrom is a initrd.img file that contains a
filesystem image.
This image is used to create a ramdisk. referencing /ks.cfg means that the
file shoud be IN that image file.
( acutally, that is what i do myself)
some good info can be found at: http://256.com/gray/docs/redhat_boot/
Matthijs Sneijders
CORUS
Research,
Development
&
Technology
Building
3G16 room
3-312
P.O. Box
10.000
1970 CA
IJMUIDEN
phone +31 (0)251-496400
fax +31 (0)251-470064
mail matthijs.sneijders at corusgroup.com
Mike
<mikeslec at gmail.com To: "General Red Hat Linux discussion list"
> <redhat-list at redhat.com>
Sent by: cc:
redhat-list-bounces Subject: custom kickstart problem
@redhat.com
30-11-2006 23:12
Please respond to
General Red Hat
Linux discussion
list
Any kickstart gurus out there?
I'm building an install CD with a kickstart cfg embedded in the iso (along
with the initrd.img, isolinux.bin, etc). According to the docs from RH,
the
kickstart file must be named ks.cfg. So I built the iso, burned it to a
CD,
but when linux boots the box it doesn't see the ks file. I tried a
multitude of cmd line entries, such ks=cdrom:/ks.cfg, etc, but no go. What
am I doing wrong?
Mike
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
**********************************************************************