<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2964" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=179004418-14052007><FONT face=Arial
color=#0000ff size=2>How many NIC's do you have in the box? Are they all
embedded, or are there some on cards?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=179004418-14052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=179004418-14052007><FONT face=Arial
color=#0000ff size=2>Kickstart is a very powerful and useful tool that we
use globally to build over 1000 distributed systems each year from a
centralized and managed location, and although it has bugs like any product,
most issues like you are having tend to be infrastructure or
manufacturer related.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> kickstart-list-bounces@redhat.com
[mailto:kickstart-list-bounces@redhat.com] <B>On Behalf Of
</B>SSTinsley@upsfreight.com<BR><B>Sent:</B> Monday, May 14, 2007 11:36
AM<BR><B>To:</B> Discussion list about Kickstart<BR><B>Cc:</B> Discussion list
about Kickstart; kickstart-list-bounces@redhat.com<BR><B>Subject:</B> Re:
Kickstart via PXE/NFS<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>I made a change to pxe cfg file to
have ks.cfg file read via http.</FONT> <BR><BR><FONT face=sans-serif size=2>It
fails too. However, if I look in the anaconda log I see the message getting
ks.cfg</FONT> <BR><FONT face=sans-serif size=2>but then failed to transfer
ks.cfg to fd. The snoop from the KS server side shows the HTTP</FONT> <BR><FONT
face=sans-serif size=2>retrieval of the KS config file. Is it really trying to
use an fd device, a floppy? These</FONT> <BR><FONT face=sans-serif size=2>Dell
servers do not include floppys.</FONT> <BR><BR><FONT face=sans-serif
size=2>Redhat sure has taken something that should be relatively easy and made
it a pain in the butt.</FONT> <BR><FONT face=sans-serif size=2> </FONT>
<BR><BR><FONT size=2><TT>kickstart-list-bounces@redhat.com wrote on 05/14/2007
01:29:54 PM:<BR><BR>> if you page-up in vty3, can you see what your kernel
command line is?<BR>> alternately if it makes it to shell in vty2, 'cat
/proc/cmdline' - i<BR>> wonder if it's actually doing the ipappend stuff. you
might need a<BR>> newer pxelinux.0 if not. also, instead of 'ksdevice=bootif'
you can do<BR>> 'ksdevice=link ip=dhcp' ; the bootif argument is more
useful if you<BR>> have 2 nics enabled/link-up and want to make sure it
doesnt pxeboot<BR>> out one interface and then ks out the other.<BR>>
<BR>> -=Eric<BR>> <BR>>
_______________________________________________<BR>> Kickstart-list mailing
list<BR>> Kickstart-list@redhat.com<BR>>
https://www.redhat.com/mailman/listinfo/kickstart-list<BR></TT></FONT>
<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.<BR></DIV></BODY></HTML>