kickstart and network configuration

[Phil Oester]

On Fri, Jul 15, 2005 at 01:50:11PM -0400, Scott Adkins wrote:
> I am having an issue with using a single kickstart for two different models
> of similar hardware (IBM Blade Center model 8678 and model 8832). 
> Apparently,
> the newer model flips its concept of what is the primary ethernet, causing
> eth1 to come up instead of eth0.  Since both interfaces actually have link
> state on them, I can't just "not specify" and expect the right one to be
> chosen.  So, I am trying to find a better way to adapt to the hardware.
> 
> First off, the line "network --bootproto dhcp --device eth1" is required to
> get the newer blades to boot.  However, it will break the older blades.

How about something like this in PRE:

if [ -n "dmidecode | grep 8678" ] ; then
   echo "network --bootproto dhcp --device eth1" > /tmp/ksnet
else
   echo "network --bootproto dhcp --device eth0" > /tmp/ksnet
fi

Then %include /tmp/ksnet where you would normally put the network
line.  Since you mention serial numbers, you could also use
that in your tests.

Phil