[comments inline]
On 5/23/2012 1:53 PM, Phil Meyer wrote:
Just to add fuel to the fire:
Soon more and more systems will have UEFI as well as, or instead of
the old BIOS. On most newer sever class systems, the traditional BIOS
is *emulated* in the EUFI.
The EUFI, and, therefore, newer BIOS, can provide much more
information to the OS than before.
Linux kernels are attempting to be more 'aware' of the new
information. It will provide much better control and flexibility with
devices.
That being said, you can avoid it all for now, by adding
'biosdevname=0' to the kernel command line in grub, or upon boot.
Already defined devices will not change, but if you include that
argument during installs, or on LiveCDs, you will get the old
consistent device names, ie: eth0, every time.
Phil:
Thanks for the reply. You just upped my reading list (smile). Let me
google with what you've provided above and what others have offered.
I've now got more than enough info to drown in and need to sort through
it before trying to get more.
The fact that two fresh installs got one old (eth0) and one new (em1)
device definition, shows the difference in the two versions of BIOS,
NOT anything to do with 64 bit vs 32 bit.
Okay, that gives me a 100% answer on that question. I just assumed out
of ignorance that it was on a Fedora level and never considered (or had
the knowledge to consider) that it might be a BIOS issue.
Good Luck!
I think I am going to need it ...
Thanks again,
Paul
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
