http://bugzilla.suse.com/show_bug.cgi?id=1168487
http://bugzilla.suse.com/show_bug.cgi?id=1168487#c2
--- Comment #2 from Bryan Gartner
This sounds like information overflow for the normal case.
If we consider this, we should first identify cases where this actually makes sense and only do it in those cases and not always.
For example, I am pretty sure that I would never want to see this on my laptop just because it has both WiFi and a (rarely used) cable Ethernet NIC.
Good callout, thanks. My request does not really apply to a single NIC system ... since the binary approach happens already, if not yet connected the flow is changed. For your example, simply displaying the wlan : DHCP : <bonus points for IPAddress> would still be quite useful for folks like me that provide many WiFi networks, even at home (guest vs. internal vs. other) to be a reminder to toggle/reconfig as needed. So perhaps just displaying any "active" NICs (if multiple NICs are present) would be sufficient as a trigger to notice ... "oh, have to adjust from main n/w to provisioning one". This is due to ensuring access to virtual media (via BMCs)/other repos as needed, instead of just hitting that obstacle later in the installer flow. -- You are receiving this mail because: You are on the CC list for the bug.