<!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=970160220-14052007><FONT face=Arial
color=#0000ff size=2>You still have never answered the question. We are
trying to help you here. It doesn't matter whether or not your second NIC
is plugged in, it does however matter whether or not it is on the same bus as
the NIC you are pxebooting from. As for why it works in pxe and doesn't
work in kickstart, they are two entirely different systems. pxe comes from
the system BIOS, and the kickstart installer comes from RHEL. The reason
this is important is because RHEL 4 + enumerates the bus differently (and
according to Red Hat properly) than either pxe or previous RHEL
versions.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2>As for "complicated", my time goes back to building
"unattend.txt" files for Windows 95 (and every version since), and kickstart is
FAR more powerful and easier to use than any of the windows technologies that
are included with the OS. And if you don't like kickstart, try using YAST
sometime, that will make you old before your time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2>This list is very helpful and has gotten many people to
quality build setups, but disparaging the tool that we are trying to help you
deploy isn't going to win friends or help.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=970160220-14052007><FONT face=Arial
color=#0000ff size=2>At the end of the day, if you don't like anaconda, do
something about it. It's open source and you can dive in and fix the
things you don't like, and submit the patches upstream. There are many
things *I* would like to see changed, but I don't have the time to write a
patch, so I have to live with it or work around it. At least now I can
make the changes if I wanted to... Sure wish I could have done that in Windows
10 years ago when I was trying to get an unattend.txt file to bring up a backup
domain controller that wasn't online with the primary since it hadn't been built
yet and was located in a different state.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Chip </FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<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 12:39
PM<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><BR><FONT size=2><TT>kickstart-list-bounces@redhat.com wrote on
05/14/2007 02:48:04 PM:<BR><BR>> How many NIC's do you have in the box?
Are they all embedded, or <BR>> are there some on cards?</TT></FONT>
<BR><BR><FONT size=2><TT>2 NICs. Only one is active an plugged in to a
switch.</TT></FONT> <BR><BR><FONT size=2><TT>While it may be powerful, it seems
to be way more complicated than should be required.</TT></FONT> <BR><BR><FONT
size=2><TT>If the server can find its initial IP via DHCP to load pxelinux and
to load the kernel, why is it</TT></FONT> <BR><FONT size=2><TT>unable to
complete the last step and locate the kickstart file? I have specified the
ksdevice </TT></FONT><BR><FONT size=2><TT>several different ways and none have
been successful (ksdevice=eth0, =link, =bootip with ipappend, =eth1)</TT></FONT>
<BR><FONT size=2><TT>and in all cases anaconda ends up unable to get the IP and
prompts me for static network configuration.</TT></FONT> <BR><FONT size=2><TT>I
enter the needed network information and provide the NFS information to reach
the RH install image and</TT></FONT> <BR><FONT size=2><TT>the box is able to
read the o/s image and start an interactive install.</TT></FONT> <BR><BR><FONT
size=2><TT>I have also dropped to command line (ctl-alt-f2) and verified that
the nfs directory holding the KS file</TT></FONT> <BR><FONT size=2><TT>can be
mounted. And I have verified it can be retrieved with http using wget. And still
anaconda is</TT></FONT> <BR><FONT size=2><TT>unable to retrieve the file with
either nfs or http.</TT></FONT> <BR><BR><BR><FONT size=2><TT>>
</TT></FONT> <BR><FONT size=2><TT>> Kickstart is a very powerful and
useful tool that we use globally to<BR>> build over 1000 distributed systems
each year from a centralized and<BR>> managed location, and although it has
bugs like any product, most <BR>> issues like you are having tend to be
infrastructure or manufacturer related.</TT></FONT> <BR><FONT size=2><TT>>
</TT></FONT> <BR><FONT size=2><TT>> From:
kickstart-list-bounces@redhat.com [mailto:kickstart-list-<BR>>
bounces@redhat.com] On Behalf Of SSTinsley@upsfreight.com<BR>> Sent: Monday,
May 14, 2007 11:36 AM<BR>> To: Discussion list about Kickstart<BR>> Cc:
Discussion list about Kickstart; kickstart-list-bounces@redhat.com<BR>>
Subject: Re: Kickstart via PXE/NFS<BR></TT></FONT><BR><FONT size=2><TT>>
<BR>> I made a change to pxe cfg file to have ks.cfg file read via http.
<BR>> <BR>> It fails too. However, if I look in the anaconda log I see the
<BR>> message getting ks.cfg <BR>> but then failed to transfer ks.cfg to
fd. The snoop from the KS <BR>> server side shows the HTTP <BR>> retrieval
of the KS config file. Is it really trying to use an fd <BR>> device, a
floppy? These <BR>> Dell servers do not include floppys. <BR>> <BR>>
Redhat sure has taken something that should be relatively easy and <BR>> made
it a pain in the butt. <BR>> <BR>> <BR>>
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</TT></FONT> <BR><FONT
size=2><TT>> NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC
<BR>> INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S)
OR<BR>> ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO
<BR>> RECEIVE IT. If you are not the intended recipient of this document,
<BR>> you are notified that any review, dissemination, distribution or
<BR>> copying of this communication is prohibited. If you have received
<BR>> this communication in error, please notify me immediately by return
<BR>> email, delete the electronic message and destroy any printed
copies.<BR>> Thank you for your
cooperation._______________________________________________<BR>>
Kickstart-list mailing list<BR>> Kickstart-list@redhat.com<BR>>
https://www.redhat.com/mailman/listinfo/kickstart-list</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>