Bug 125521

Summary: 9.4. Kickstart Options -> network -> installing from eth1
Product: Red Hat Enterprise Linux 3 Reporter: Thomas Uebermeier <uthomas>
Component: rhel-sagAssignee: Sandra Moore <smoore>
Status: CLOSED NOTABUG QA Contact: John Ha <jha>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: adstrong, andriusb, katzj
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-08 19:55:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 123819    

Description Thomas Uebermeier 2004-06-08 14:35:56 UTC
Description of problem:

- 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:
Actual results:

Expected results:

Additional info:

Comment 4 Andrius Benokraitis 2005-02-03 20:16:47 UTC

Do you mean what's shown at:



    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.

Comment 5 Andrius Benokraitis 2005-02-08 19:55:52 UTC
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!

Comment 6 Thomas Uebermeier 2005-02-09 08:48:47 UTC
yes you can keep the bug as closed. ksdevice is the right option.