Re: More on Re: Really changing the hostname

[Les Mikesell <lesmikesell@xxxxxxxxx>]

On Fri, Feb 15, 2013 at 2:55 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
>
>> You still have to deal with at least one file, and if you can fix one
>> it's not that much harder to fix two.   Almost all of our machines
>> (virtual and real) have multiple interfaces.
>
> so what - why should i edit 2 files if one is enough
>
>>>> In either case I am somewhat nervous about
>>>> depending on files that sometimes magically get re-written - and don't
>>>> really understand the things that can trigger it
>>>
>>> call your interfaces in "70-persistent-net.rules" "lan0", "lan1",
>>> "wan0" and change "ifcfg-eth*" to match and this will not happen
>>
>> If the system re-writes 70-persistent-net.rules itself, the names will
>> change and the NIC ordering is unpredictable.  And if you script a
>> fixup, it's just another line or two to fix the matching ifcfg-*
>> files
>
> you do not understand what i have said
>
> the race between kernel enumeration and udev is the reason
> why it is unpredictable, do not use the kernel names on machines
> with more than one interfaces and NOTHING will fuckup your
> "lan0", "lan1"....

I don't understand how you create that udev entry before you need it.
 Or why one udev-assigned name is different from any other name once
it is in place in that file.

-- 
   Les Mikesell
     lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos