From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 12: | Line 12: | ||
== What to test? == | == What to test? == | ||
Today's | Today's instalment of Fedora Test Day will focus on '''[[Features/ConsistentNetworkDeviceNaming#Consistent_Network_Device_Naming|Network Interface Naming]]'''. | ||
Traditionally network interfaces in Linux are named ethN. With multiple network adapters, both onboard and add-in, single and multiport, in modern server platforms, the naming of these interfaces is non-deterministic. Specifically, ''eth0'' does not always map to ''Gb1'' or ''Embedded NIC 1'' as named on the server chassis. This makes the existing naming not very user friendly for administration. Β | Traditionally network interfaces in Linux are named ethN. With multiple network adapters, both onboard and add-in, single and multiport, in modern server platforms, the naming of these interfaces is non-deterministic. Specifically, ''eth0'' does not always map to ''Gb1'' or ''Embedded NIC 1'' as named on the server chassis. This makes the existing naming not very user friendly for administration. Β |