How can I prevent udevd from renaming eth0 to em1

Bill Davidsen davidsen at tmr.com
Tue Oct 23 21:42:43 UTC 2012


Digimer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 10/22/2012 12:15 AM, Michael H. Warfield wrote:
>> On Sun, 2012-10-21 at 23:02 -0500, Bruno Wolff III wrote:
>>> On Sun, Oct 21, 2012 at 13:43:17 -0400, "Michael H. Warfield"
>>> <mhw at WittsEnd.com> wrote:
>>>>
>>>> Now that being said, there's still some notable differences.
>>>> Most of my machines (some F16 and some F17, some i686 and some
>>>> x86_64) came up with p2p1 for interface names and his is coming
>>>> up em1.  Obviously something
>>
>>> em1 would be the first embedded nic. Probably its built into the
>>> motherboard. p2p1 is a nic attached to the pic bus. I think its
>>> the second slot, first port. (Probably the card has only one
>>> port, but some have more than one.)
>>
>> Ok...  And that then makes it even weirder since all my Dell
>> towers (Optiplex GX620 x86_64 machines and Optiplex GX280 i686
>> machines) are all uniformly coming up p2p1 for the motherboard nic
>> (they don't have any add-on nics).  Maybe it's the way they are
>> designed...  IAC, my Dell 2U PowerEdge helped me diagnose the
>> problem and chase it into the initramfs and biosdevname.
>>
They may be on an internal PCI bus and look external, I'm not sure how 
"embedded" a NIC is to be recognized as such.

>> Thanks!
>>
>> Regards, Mike
>
> It's an imperfect science. My onboard NICs also come up as p1p1 and p1p2.
>
> - --
> Digimer
> Papers and Projects: https://alteeve.ca/w/
> What if the cure for cancer is trapped in the mind of a person without
> access to education?


-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


More information about the users mailing list