I made a change to pxe cfg file to have ks.cfg file read via http. It fails too. However, if I look in the anaconda log I see the message getting ks.cfg but then failed to transfer ks.cfg to fd. The snoop from the KS server side shows the HTTP retrieval of the KS config file. Is it really trying to use an fd device, a floppy? These Dell servers do not include floppys. Redhat sure has taken something that should be relatively easy and made it a pain in the butt. <tt>kickstart-list-bounces@redhat.com wrote on 05/14/2007 01:29:54 PM: > if you page-up in vty3, can you see what your kernel command line is? > alternately if it makes it to shell in vty2, 'cat /proc/cmdline' - i > wonder if it's actually doing the ipappend stuff. you might need a > newer pxelinux.0 if not. also, instead of 'ksdevice=bootif' you can do > 'ksdevice=link ip=dhcp' ; the bootif argument is more useful if you > have 2 nics enabled/link-up and want to make sure it doesnt pxeboot > out one interface and then ks out the other. > > -=Eric > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list </tt> <DIV> NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not the intended recipient of this document, you are notified that any review, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify me immediately by return email, delete the electronic message and destroy any printed copies. Thank you for your cooperation. </DIV>