RE: backwards NIC's durring install/kickstart

["Shabazian, Chip" <Chip Shabazian bankofamerica com>]

RHEL4 enumerates the bus backwards from what prior versions did.  I
believe Red Hat states that they are properly enumerating the bus, and
have always done it backwards prior to now.  Anyway, why not use
ksdevice=MAC_ADDRESS.  That's what we do. 

-----Original Message-----
From: kickstart-list-bounces redhat com
[mailto:kickstart-list-bounces redhat com] On Behalf Of Matt Sturtz
Sent: Tuesday, January 16, 2007 12:25 PM
To: kickstart-list redhat com
Subject: backwards NIC's durring install/kickstart

All--

I think this might have been covered in the last few weeks...

I'm installing on Dell 1955 servers and whitebox (Intel motherboard)
servers.  It seems that eth0 becomes eth1 and vice-versa in RHEL-4
update-4 based systems.  It would seem that if I omit my ksdevice kernel
option and my --device option is ks.cfg, that it works (I get a prompt,
choose eth1).  It also seems that kernel 2.6.9-42.0.3 has the same
issue, so it's not limited to only the BOOT kernel.  If I disable the
second NIC in the bios, the first nic is (correctly) eth0.

Was there any fix for this?  Aside from being generally annoying, my
kickstart scripts use the MAC address of eth0 to identify the system,
but since eth0 is now eth1, the system can't find its scripts...

-Matt-

_______________________________________________
Kickstart-list mailing list
Kickstart-list redhat com
https://www.redhat.com/mailman/listinfo/kickstart-list