|
yes,
you need to place the ks.cfg inside of your boot.img on the
cdrom,
Step
1
Copy
the whole of the redhat distribution onto you local HD, make sure you get the
hidden . files in the cd roots etc, as well (ls -la)
Step
2
mount
the cdrom and make a backup of the boot image on the cdrom.
$
mount -o loop the boot image,
$
ls /<mount point boot image> and you will see the
initrd.img,
copy
the initrd.img out of the boot image to initrd.bak
copy
initrd.bak to initrd.img.gz,
$
gunzip initrd.img.gz
$
mount -o loop the resulting initrd.img
$ cd
/<mount point of intrd.img>
you
will see a ks/ directory, inside lives the ks.cfg file,
$ cp
/<mount point of intrd>/ks/ks.cfg locally i.e.
ks.cfg_testing
make
your changes to ks.cfg_testing
$ cp
ks.cfg_testing /<mount point of intrd.img >/ks/ks.cfg
(overwrite ks.cfg <yes>)
$
umount /<mount point of intrd>/
$ gzip
initrd
$ cp
initrd.img.gz /<mount point boot image.img>/initrd.img (overwrite
initrd.img <yes>)
Step
3
Now
syslinux.cfg
in the /<mount point boot image> you
will see syslinux.cfg and a bunch of other files
change syslinux.cfg to read:
<-------------------- Start of file
------------------------>
default ks
prompt 1 timeout 10000 display boot.msg F1 boot.msg F2 install.msg F3 hardware.msg F4 raid.msg label ks kernel vmlinuz append ks=file:/ks/ks.cfg initrd=initrd.img <-------------------- End of file
------------------------> $
umount /<mount point boot image>
you
now have your ks.cfg inside the initrd in the boot image of the
cdrom.
and
you have syslinux.cfg inside the boot.img pointing to it.
Step
4
On a
linux box create the new iso. Go into your iso creation directory
and
mkisofs -b your_boot.img -c boot.cat -r -o $ISO_NAME
.
this
will make a recordable bootable redhat .iso
N.B.
if you are doing the kickstart only from CD-rom you will have to munge the 2 CD
set /RedHat/RPMS/ together this is covered in many docs on the net. First thing
you will find is all the rpms together are to big to fit on 1
CD-rom.
good
luck.
yours
a.r.b.
|
