[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re (2): dreaded ethernet device renaming



From:	briand@aracnet.com
Date:	Thu, 31 Mar 2011 07:34:32 -0700
> It seems to me that this is a really ugly user trap, even if it's a
> trap you get into replacing the old motherboard.

In the Linux world, udev is really a beautiful way of handling 
contemporary peripheral devices.  eth0, eth1 ... worked for the 
ISA bus.  Now devices are hot-swappable.  A more general naming 
mechanism is needed. 
http://en.wikipedia.org/wiki/Hot_swapping

> It was already eth0, what possible reason could it have to go rename it.

You added a NIC which udev hadn't identified previously? 
udev decided to call it eth0?  Something similar?

udev was doing its best under the conditions you imposed and 
you can easily give each NIC a unique name.  Here is an example.
  "http://142.103.107.138/NetworksPage.html#NICnames";
If it doesn't make sense let me know.
  
Just for sake of interest, device management in A2 has automatically 
assigned meaningful names since several years ago.  Nothing such as 
/etc/udev/rules.d/*.rules is involved. 
  "http://en.wikipedia.org/wiki/Bluebottle_OS";

Regards,                     ... Peter E.



-- 
Telephone 1 360 450 2132.
Shop pages http://carnot.yi.org/ accessible as long as the old drives survive.
Personal pages http://members.shaw.ca/peasthope/ .


Reply to: