Charles
Charles Steinkuehler wrote:
...
>
> The problem is most of the time if you have multiple NICs, they use the
> same chipset. That means the ethX order is determined by the device
> driver, not by the module load order, and the device drivers have no
> standardized way of indicating which physical interface is "first".
Implemented as specified...
>
> So...either something has to talk to the kernel the way modprobe, udev,
> etc. manage to do, or a different approach is needed (perhaps using MAC
> addresses or logical names to identify the interfaces instead of ethX).
>
How would a logical name survive a reboot? I guess the only fixed
identification would be the mac address.
cheers
Erich
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
