Not sure this is exactly the same, but may help. In our environment we install over NFS, but the ks.cfg is on boot floppy. We had to modify the file syslinux.cfg on the bootdisk.img to make the install non-interactive and point to the ks.cfg. The following diff command shows what we changed: diff <my syslinux.cfg> <standard syslinux.cfg> 2c2 < prompt 0 --- > prompt 1 13c13 < append ks=floppy initrd=initrd.img ramdisk_size=8192 --- > append initrd=initrd.img ramdisk_size=8192 -alan -----Original Message----- From: Andy Elmer [mailto:Andy.Elmer@xxxxxxxx] Sent: Thursday, November 20, 2003 5:25 PM To: fedora-list@xxxxxxxxxx Subject: kickstart problems Has anyone else had success using kickstart via NFS with Fedora? I am doing everything the same way I always have with RH 7.3, 8, and 9. Has the ks.cfg format changed? In our environment the ks.cfg files come from dhcp. I have updated the Fedora ks.cfg files appropriately which was based on our Redhat ks.cfg's ( ie changed the NFS path of the fedora media, changed package list appropriately, etc). When I tried to kickstart a box, fedora loads its kernel, gathers its info from DHCP, but then starts its *interactive* install. Basically it appears its not getting the ks.cfg file or something is misconfigured. Anyway, I just curious if others have successfully loaded Fedora via NFS kickstart. If so, it must be something I'm doing wrong (I'm was doubtful since I've been doing this type of installation for quite a while). Thanks! Andy -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
