netdev - Re: Network Device Naming mechanism and policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Mar 2009 14:12:03 -0400
From:	Bill Nottingham <notting@...hat.com>
To:	Matt Domsch <Matt_Domsch@...l.com>
Cc:	Scott James Remnant <scott@...ntu.com>, netdev@...r.kernel.org,
	linux-hotplug@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Network Device Naming mechanism and policy

Matt Domsch (Matt_Domsch@...l.com) said: 
> > Now consider USB.  Would the device name change depending on which USB
> > port you plugged it into?  Or is USB just a single slot, in which case
> > what happens when you have two USB ethernet devices?
> > 
> > The Apple USB Ethernet device in my iPhone is not the USB Wireless
> > adapter I own, both have very different networking configurations.
> 
> we would obviously need a solution.  eth_usb_{something} perhaps.

Right, but having biosdevname chase each new bus that comes along
sounds iffy. I'd prefer /dev/net/by-name symlinks, if at all
possible. But that's a lot of code that I'm not prepared to write.

Bill
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html