Description of Problem:
It's very difficult to match ethX<->physical ethernet jack on systems with more
than one ethernet jack. Consider the case where we install seven dual-port
NICs plus have two embedded NICs. The guy in the factory won't always know
which jack matches eth0 which the installer needs to know.
Anaconda loader should, during network installs (particularly kickstart
installs), try to obtain DHCP addresses and contact the network server, for all
ethX devices found, before falling back to CD-ROM installs as it currently
does. Perhaps keep the DHCP timeout short - if a cable isn't attached to that
port, you don't want a 2+ minute timeout, times the number of NIC ports, to
figure that out.
Ideally this would be implemented for both Pensacola and Hampton.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Jeremy do you think this is doable on a Hampton timescale?
It certainly is not doable for Pensacola.
Possibly for Hampton, largely dependent on what else breaks and requires fixing.
Also, when it is done, it will probably require a special boot option to enable
as for the general case, it is not the desired behavior due to the much longer
period of time it will cause if you have to cycle through and timeout on
boot option and/or kickstart directive would be fine. boot option gives more
flexibility as to where we put ks.cfg then.
THIS BUG IS 10 MONTHS OLD (pre 7.3?). IS THIS STILL ACTIVE? If not, we should
close this bug. NOTE: Not in Feature Tracker.
OPENED FEATURE TRACKER #800 for this Bugzilla.
Jeremy was thinking of implementing ksdevice=any.
Added ksdevice=link which will use the first device with an apparently active link.
Thanks much, will test and open bugs if necessary. Closing feature request.