[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] eth numbering change
- Subject: [ale] eth numbering change
- From: philip at turmel.org (Phil Turmel)
- Date: Thu, 9 Feb 2017 15:44:28 -0500
- In-reply-to: <[email protected]>
- References: <CAFc0yP3L7=mA3YrW_OgvxZc5_i1dbQ5kS3T7P54FCVojocriVQ@mail.gmail.com> <[email protected]> <CAFc0yP0koNJNBQTJ3jKzV=pH5++Qwiq=bxDdJ6tWSCt0cybcjA@mail.gmail.com> <[email protected]> <[email protected]>
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