On 10/16/2012 01:17 PM, sirdeiu wrote:
I just edited 71-biosdevname.rules in /lib/udev/rules.d, where line 15 contains:
*GOTO="netdevicename_end"*
Basically just uncomment it like the instruction above it said.
Then all my NIC's are named ethX. Also name them accordingly in your /etc/sysconfig/network-scripts/ifcfg-ethX files.
This was the best approach for me.
PS: Might change on an update of biosdevname or whatever creates that rules file.
I have no such file on my fc16 system, because I deleted the biosdevname package. What a useless package that does not solve anything, but creates new problems for everyone.
On Tue, Oct 16, 2012 at 01:56:51PM -0600, JD wrote:
What a useless package that does not solve anything, but creates new problems for everyone.
That's really not the case. It may not solve anything for *you*, but it does address a real problem. Maybe not perfectly, but we can fix the bugs.
Matthew Miller wrote:
On Tue, Oct 16, 2012 at 01:56:51PM -0600, JD wrote:
What a useless package that does not solve anything, but creates new problems for everyone.
That's really not the case. It may not solve anything for *you*, but it does address a real problem. Maybe not perfectly, but we can fix the bugs.
The first step is to realize that your solution is viewed as a bug by many people. The very server people this was supposed to help will tell you that a naming convention which changes the name if you plug a NIC into a different slot doesn't fit their labels on cables and NICs. Not to disparage any vendor, but moving cards to address thermal issues isn't rare. I know some sites like to label slots so a failing NIC can be swapped, but honestly the days of failing NICs on server grade equipment have been gone for a few decades now.
Any machine with a single NIC should get it named eth0, which is backward compatible and probably represents the majority of Fedora users.
-
Bill Davidsen -
JD -
Matthew Miller