Hide Forgot
On a machine with TWO ethernet cards there is an option to configure only the one during an installation. This would be fine if not that small detail that the other card is configured by default to DHCP and ONBOOT=yes. The effect is that on the first boot a machine makes a pretty good impression that it hanged trying to bring eth1 up. It times out, eventually, but a timeout period is long enough to convince a newbie that the whole thing crashed. In my particular case there was not even a cable connected to eth1. Otherwise this may possibly take even longer because DHCP would have to be sent and timeouts for these would possibly have to be added. Yes, there will be the second cable here, but later.
Did you install in GUI or text mode?
This was GUI install. I do not know what will happen with text. Actually there are reasons for a cable to be connected right now to eth1, but this is a side issue.
Did you look at the screen where it lets you configure eth0 to see if there is a notebook tab at the top for eth1 as well?
I did not notice any tabs; but it cannot be entirely excluded that I am blind.
Brent please investigate this case. I would agree we should only default the first nic (eth0) to DHCP, and the others to manual configuration and onboot=no unless they supply values. Will have to address next release cycle, deferring for now.
Jeremy please check this behavior with enigma.
This should be fixed as of Red Hat Linux 7.2. If you find this not to be the case, please reopen this bug report.