Hi, I have seen a tremendous amount of questions on this mailing-list regarding kickstarting with a ks.cfg directly off the cdrom, and like Forrest have said that it does not work... I wasn't comfortable with that conclusion and 2 days ago I set out to track down a solution to what appeared to be (and in fact is) a bug with the RH7.1 anaconda /sbin/loader program found in the initrd.img of boot.img. I tracked down a patch on redhat's bugzilla (actually saw an indirect reference to the cdrom problem bug on this list), the patch that fixes the ks=cdrom:<path> bug can be found here: http://bugzilla.redhat.com/bugzilla/showattachment.cgi?attach_id=22767 I applied this patch to anaconda-7.1, and then built a fixed 'loader' (need to type 'make loader' in <anaconda_7.1_src>/loader/).. I then replaced the 'loader' as found in the initrd.img within boot.img, expanded the image to be 2.88MB for future expansion capabilities for Paralogic's Beowulf Cluster distribution needs.. I then added an entry like this to syslinux.cfg: label node1 kernel vmlinuz append ks=cdrom:/cluster/node1/ks_cd.cfg initrd=initrd.img lang= devfs=nomount created an iso with the following script: #!/bin/sh mkisofs -v -r -T -J -b images/boot288.img -c boot.cat -o $1.iso $1 I burnt the iso and believe it or not IT WORKED! Kickstarting from cd is made much easier when you don't need to modify the initrd.img every time you'd like to tweak a ks.cfg. Hope all this helps, Mike Taylor, ForrestX (forrestx.taylor@xxxxxxxxx) said: > > "Taylor, ForrestX" wrote: > > > That should work. You don't want to use ks=cdrom:... > > because it won't work. > > > Are you doing Red Hat 6.2 or 7.x? > > > > > > Forrest > > > Hi > > > > I am using 7.1 I tried the ks=file:/ks.cfg when the ks.cfg was in the > > root of my compressed initrd.img this didnt even try to read > > the ks.cfg > > but went straight into a normal install. Once I put the > > ks.cfg in the / > > of the normal cdrom filesystem it did , but then gave Cannot find > > /tmp/ks.cfg > > > > S. > > > > > > -- > > Stephen Johnston > > I have always done it this way, and it has always worked. When it says that > it cannot find /tmp/ks.cfg, that means that it couldn't find your ks.cfg to > copy to /tmp. This is what I use in syslinux.cfg when I have my ks.cfg file > in the compressed initrd.img: > > default ks > prompt 1 > timeout 60 ... > > label ks > kernel vmlinuz > append ks=file:/ks.cfg initrd=initrd.img lang= devfs=nomount > > This will wait 6 seconds at the boot prompt, and then continue using the ks > label. Did you use something similar? Did you run genhdlist before you > created the CD? > > Forrest > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
