This is done in two parts:
1. in syslinux.cfg to specify where to get the ks.cfg from and
2. in ks.cfg to determine which interface to get access the installation
files.
syslinux.cfg:
append ks=nfs:192.168.0.1:/var/ftp/pub/kickstart/rh9-notify-ks.cfg
initrd=rh9-stock-pxeboot-initrd.img ksdevice=eth0
ks.cfg:
network --bootproto=dhcp --device=eth0
This works great on my boxes that have 2 network cards.
Sincerely,
Richard Black
Adam Glass wrote:
I'm trying to Kickstart a machine with multiple Ethernet interfaces.
I'm using RH9.0. I have what I think is a reasonable Kickstart config
file, but the installer disagrees. :) It pops up a message saying:
"You have multiple interfaces on this system. Which would you like to
install through?" (Once I give it one, it continues along just fine.)
Now, I know that the "network" configuration directive can take a
"--device=" argument that is "Used to select a specific Ethernet
device for installation." Unfortunately, the documentation goes on to
say that "--device= will not be effective unless the kickstart file is
a local file (such as ks=floppy)" ... which it's not; it was retrieved
via NFS. Google searches and the Redhat documentation have let me
down. Surely there is someone out there doing this... ?
TIA,
Adam
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
