[ale] eth numbering change

[Lightner, Jeffrey]

There are, unfortunately, some applications that fail if they don't find eth# names.

We've run across that with the newer location specific names available on some servers (e.g. Dell PowerEdge).   The location names are better because they tell you where the NIC is.   Not all servers or NICs do that but it is nice to see at a glance which NICs are on the motherboard or in slots.

-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of Phil Turmel
Sent: Thursday, February 09, 2017 3:44 PM
To: ale at ale.org
Subject: Re: [ale] eth numbering change

On 02/09/2017 12:19 PM, Alex Carver wrote:
> On 2017-02-09 09:15, Phil Turmel wrote:

>> This is also true for hard drives.  And all of this is precisely the 
>> reason udev persistent name rules were created, and blkid label and 
>> uuid names are used.
>>
>> Don't use ethX names with modern kernels.  Period.
>>
>> Phil
> 
> I wouldn't say never.  I had one installation that steadfastly refused 
> to boot properly with UUIDs for the disk.  It was a very recent 
> kernel, too, which made it much more confusing.  I had to force it 
> back to using /dev/sdAN references to get things working.

The kernel doesn't process any of the naming schemes.  It all goes to udev, which must be in the initramfs to boot off of a LABEL or UUID root.  What you described is an initramfs failure.

Phil
_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo