From: Scott James Remnant <scott@ubuntu.com>
To: Bill Nottingham <notting@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Network Device Naming mechanism and policy
Date: Tue, 24 Mar 2009 18:20:07 +0000 [thread overview]
Message-ID: <1237918807.22009.47.camel@quest> (raw)
In-Reply-To: <20090324181202.GE5925@nostromo.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Tue, 2009-03-24 at 14:12 -0400, Bill Nottingham wrote:
> Matt Domsch (Matt_Domsch@dell.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.
>
Not to mention that All The World Is Not x86
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-24 18:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 15:46 Network Device Naming mechanism and policy Matt Domsch
2009-03-24 15:46 ` Matt Domsch
2009-03-24 16:21 ` Patrick McHardy
2009-03-24 16:21 ` Patrick McHardy
2009-03-24 16:28 ` Kay Sievers
2009-03-24 16:28 ` Kay Sievers
2009-03-24 16:38 ` Patrick McHardy
2009-03-24 16:38 ` Patrick McHardy
2009-03-24 16:40 ` Dan Williams
2009-03-24 16:40 ` Dan Williams
2009-03-24 17:00 ` Alan Cox
2009-03-24 17:04 ` Patrick McHardy
2009-03-24 17:04 ` Patrick McHardy
2009-03-24 18:51 ` david
2009-03-24 18:51 ` david
2009-03-24 21:02 ` Alan Cox
2009-03-24 23:14 ` Greg KH
2009-03-24 23:14 ` Greg KH
2009-03-24 16:42 ` Karl O. Pinc
2009-03-24 16:42 ` Karl O. Pinc
2009-03-24 17:45 ` Matt Domsch
2009-03-24 17:45 ` Matt Domsch
2009-03-24 17:02 ` Scott James Remnant
2009-03-24 17:52 ` Matt Domsch
2009-03-24 17:52 ` Matt Domsch
2009-03-24 18:12 ` Bill Nottingham
2009-03-24 18:12 ` Bill Nottingham
2009-03-24 18:20 ` Scott James Remnant [this message]
2009-03-24 18:49 ` david
2009-03-24 18:49 ` david
2009-03-24 19:22 ` Matt Domsch
2009-03-24 19:22 ` Matt Domsch
2009-03-24 22:57 ` David Miller
2009-03-24 22:57 ` David Miller
2009-03-25 20:22 ` Chris Friesen
2009-03-25 20:22 ` Chris Friesen
2009-03-26 20:17 ` Dan Williams
2009-03-26 20:17 ` Dan Williams
2009-03-26 16:39 ` Matt Domsch
2009-03-26 16:39 ` Matt Domsch
2009-03-26 20:16 ` Dan Williams
2009-03-26 20:16 ` Dan Williams
2009-03-27 16:06 ` Len Brown
2009-03-27 16:06 ` Len Brown
2009-04-09 14:58 ` Matt Domsch
2009-04-09 14:58 ` Matt Domsch
2009-03-31 14:07 ` Kurt Van Dijck
2009-03-31 14:07 ` Kurt Van Dijck
-- strict thread matches above, loose matches on Subject: below --
2009-08-05 19:50 Jordan_Hargrave
2009-08-05 21:49 ` Alan Jenkins
2009-08-06 8:15 ` Alan Jenkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1237918807.22009.47.camel@quest \
--to=scott@ubuntu.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=notting@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.