|Summary:||[RFE?] anaconda-ks network lines with multiple NICs|
|Product:||[Retired] Red Hat Linux||Reporter:||Mike McLean <mikem>|
|Component:||anaconda||Assignee:||Jeremy Katz <katzj>|
|Status:||CLOSED RAWHIDE||QA Contact:||Mike McLean <mikem>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-04-24 18:34:37 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Mike McLean 2002-11-26 17:17:53 UTC
* -re1125.nightly On a machine with two network cards, I selected only one network card to be activated. The resulting anaconda-ks had two network lines (is this even allowed?), with no indication that one should not be activated on boot. When there are two network lines, how does anaconda chose which one it will use for its own network config during the install? If both specify nameserver or hostname, which one wins? Can we add an option to the network command to indicate whether or not the device should be enabled on boot?
Comment 1 Michael Fulbright 2003-08-25 21:27:50 UTC
Comment 2 Jeremy Katz 2006-04-24 18:34:37 UTC
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be fixed). If any of these are still a problem, please reopen or file a new bug against the release which they're occurring in so they can be properly tracked.