Description of problem: https://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-kickstart2-options.html - installing RHEL through kickstart - having more than one network interfaces on the machine - kickstart searches on the interface, that ist defined as the first in ks.cfg for the NFS server This behaviour should to be added to the documentation (maybe even as feature on redhat-config-kickstart ?) Version-Release number of selected component (if applicable): current online documentation How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Thomas: Do you mean what's shown at: http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/s1-kickstart2-startinginstall.html ksdevice=<device> The installation program will use this network device to connect to the network. For example, to start a kickstart installation with the kickstart file on an NFS server that is connected to the system through the eth1 device, use the command ks=nfs:<server>:/<path> ksdevice=eth1 at the boot: prompt.
Thomas, haven't heard back from you on this, and our deadline for RHEL4 documentation is looming. Please contact me to reopen the bug or for more clarification! Thanks so much!
Andrius, yes you can keep the bug as closed. ksdevice is the right option.