| 1 |
On 29/03/2013 12:34, Chí-Thanh Christopher Nguyễn wrote: |
| 2 |
> Diego Elio Pettenò schrieb: |
| 3 |
>> > If my desktop only has one Ethernet interface, no matter how many kernel |
| 4 |
>> > changes happen, it'll always be eth0. |
| 5 |
> That was not true with the old persistent naming. One example which we |
| 6 |
> encountered in #gentoo IRC was the split between e1000 and e1000e drivers |
| 7 |
> which caused interfaces to change names. |
| 8 |
|
| 9 |
Okay let me re-qualify the statement: |
| 10 |
|
| 11 |
"If my desktop only has one Ethernet interface, and I don't mess up with |
| 12 |
it in userspace at all, no matter how many kernel changes happen, it'll |
| 13 |
always be eth0". |
| 14 |
|
| 15 |
Yes, the previous persistent rules for udev would have messed that one |
| 16 |
up when e1000e got split, or if you switched between the |
| 17 |
Broadcom-provided driver to the kernel one or vice-versa. The deathforce |
| 18 |
drivers come in mind as well. |
| 19 |
|
| 20 |
> |
| 21 |
>> > Whereas, with the new predictable scheme, if I move that card around, it |
| 22 |
>> > will change name. |
| 23 |
> It's even worse, if you mess with kernel parameters (esp. pci=assign-busses |
| 24 |
> for PCMCIA) then the device numbering might change without hardware moving |
| 25 |
> around. |
| 26 |
|
| 27 |
Sweet I didn't think about that. Yai for predictably variable names. |
| 28 |
|
| 29 |
-- |
| 30 |
Diego Elio Pettenò — Flameeyes |
| 31 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
Archives