Timothy E. Miller wrote:
Hi guys and gals,
I'm trying to automate cluster installation using kickstart and
16 IBM x335 nodes that have dual 10/100/1000 Broadcom ethernet
adapters (on board).
The kickstart docs in anaconda-7.3 say that if I don't specify
a "network" option in the config file that Kickstart/Anaconda
will assume that the install is supposed to use eth0 and DHCP.
However, once the nodes remote boot via PXE, the install process
stops (argh!), tells me I have two interfaces, and then asks which
one I'd like to install over.
I want this fully automated for obvious reasons. Is there some
hidden/secret combination of commands to get around this prompting?
The non-package portions of the ks.cfg are shown below.
Thanks!
-Tim
From the manual
(http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-kickstart2-options.html)
--device <device>
Used to select a specific Ethernet device for installation. Note
that using --device <device> will not be effective unless the kickstart
file is a local file (such as ks=floppy), since the installation program
will configure the network to find the kickstart file. Example:
network --bootproto dhcp --device eth0
Forrest
--
