howdy, I presume (since you are burning your own cds) you want to throw the kickstart file(s) onto the cd. RH7.0 and RH7.1 (not sure about 7.1) have a bug (take a look at bugzilla) in terms of: you cant put the ks file onto the cd and then (at the prompt) type: linux ks=cdrom:/<pathtofile> it just wont work if you use the ks=cdrom method, there is a patch available, somewhere, no idea where. But in your case (since yu want to automate things anyway) I would suggest using ks=file:/<filetopath> This works for me, in this case, you have to put the ks file(s) into the initrd.img image file which is located on the boot disk of redhat: You'll find the boot.img boot disk image (this is the same image that is used when you boot from the cd, or at least I think so) on the redhat cd in the /images directory, mount it loopback mount -o loop boot.img /mnt/test then, take a look at the syslinux.cfg on the disk, its a text file, and adding you own options to it is a pice of cake, actually, this lets you (very easily) select between different kickstart files. I for instance have one for regular kickstart, one for upgrade and one for software raid, take a look at my syslinux.cfg file: default linux prompt 1 timeout 0 display boot.msg F1 boot.msg F2 general.msg F3 expert.msg F4 param.msg F5 rescue.msg label linux kernel vmlinuz append initrd=initrd.img lang= devfs=nomount vga=788 label text kernel vmlinuz append initrd=initrd.img lang= text devfs=nomount label expert kernel vmlinuz append expert initrd=initrd.img lang= devfs=nomount label kickstart kernel vmlinuz append ks=file:/ks/ks-71-1-install.cfg initrd=initrd.img label kickstart-upgrade kernel vmlinuz append ks=file:/ks/ks-71-1-upgrade.cfg initrd=initrd.img label kickstart-raid kernel vmlinuz append ks=file:/ks/ks-71-1-raid.cfg initrd=initrd.img label nofb kernel vmlinuz append initrd=initrd.img lang= devfs=nomount nofb label lowres kernel vmlinuz append initrd=initrd.img lang= lowres devfs=nomount so basically you just have to put the kickstart file into the initrd.img, mount it loopback again (you will have to gunzip it, since its compressed, use "gzip -9" to compress again) Once you have this you should take a look at this how-to, which I think someone posted on this mailing list some time ago: This one for 6.x http://www.imsb.au.dk/~mok/linux/doc/RedHat-CD.html This one for 7.x http://cambuca.ldhs.cetuc.puc-rio.br/RedHat7-CDs-HowTo.html I guess the main problem you run into is that redhat now comes on two cds and a few key things are different when building two cds. cheers, frosty On Mon Aug 20, 2001 at 11:09:42AM +0200, the legend Stephen Johnston <sjohnsto@xxxxxxx> wrote to me: > Hi > > We wish to create a KS cd-rom and I am interested in using syslinux but > need to know about how this works, I have found using a lilo ramdisk to > enable creation of an el-torito cd to be _really_ complicated and am > utterly confused, so I would be grateful if someone could direct me to > recent docs on the subject? > > Regards, > > Stephen. > > -- > Stephen Johnston Phone: +49 89 > 32006563 > NGAST Advanced Project Fax : +49 89 > 32006380 > European Southern Observatory > Karl-Schwarzschild-Strasse 2 > D-85748 Garching bei Muenchen > http://www.eso.org/~sjohnsto > -- > Faster than a speeding syrup. > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list -- pub 1024D/F895FC6A 2001-04-24 Erik Gostischa Franta (frosty the snowman) <frosta718@xxxxxxx> sub 2048g/85DD8AC3 2001-04-24
