| 1 |
On Wed, Jan 16, 2013 at 10:19 AM, Tobias Klausmann <klausman@g.o> wrote: |
| 2 |
> Hi! |
| 3 |
> |
| 4 |
> On Tue, 15 Jan 2013, Greg KH wrote: |
| 5 |
>> So anyone who relies on network names right now to be deterministic, and |
| 6 |
>> you have more than one network device in your system, should seriously |
| 7 |
>> reconsider how they are naming their devices, as it will not work if you |
| 8 |
>> only rely on the kernel. |
| 9 |
>> |
| 10 |
>> You might have gotten "lucky" for the past 5 years, but you never know |
| 11 |
>> what could happen if you reboot today. Seriously, I've seen it happen |
| 12 |
>> all the time. |
| 13 |
> |
| 14 |
> It has been rather nifty that if I walk up to a random machine |
| 15 |
> with exactly one NIC (that I've been asked to examine/fix), I |
| 16 |
> _know_ that there will be eth0 and only that. |
| 17 |
> |
| 18 |
> OTOH, maybe it's a good idea to make admins do "ip link sh" and |
| 19 |
> "ip addr sh" every time they examine a new computer -- it goes a |
| 20 |
> long way to root out wrong assumptions in that field. |
| 21 |
> |
| 22 |
> Regards, |
| 23 |
> Tobias |
| 24 |
> |
| 25 |
> PS: Do not use ifconfig. Ever. Except if there's no iproute. And |
| 26 |
> then you should only use ifconfig to enable downloading of |
| 27 |
> iproute :) |
| 28 |
> |
| 29 |
|
| 30 |
I would actually like to see iproute2 added to the system set. |
Archives