From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Larry Finger <larry.finger@lwfinger.net>,
Pavel Roskin <proski@gnu.org>, Alex Davis <alex14641@yahoo.com>,
linux-wireless@vger.kernel.org
Subject: Re: Patch to allow specification of interface name prefix
Date: Tue, 27 Feb 2007 20:25:00 -0500 [thread overview]
Message-ID: <20070228012500.GB4072@tuxdriver.com> (raw)
In-Reply-To: <43e72e890702271055sc1525ecy54870626125a7fae@mail.gmail.com>
On Tue, Feb 27, 2007 at 01:55:07PM -0500, Luis R. Rodriguez wrote:
> adopt eth%d convention. With SoftMAC (mac80211) things are a bit
> different -- wmaster handles 802.11 frames and wlan%d handles 802.3
> frames. The name does not matter much but it does imply at least that
> I think. As such perhaps mac80211 should change to use eth%d by
> default.
Hopefully wmaster will fall off the user's radar soon. Regarding the
current wlanX interfaces, most modes will be using ethernet framing,
so maybe ethX is fine. What about monitor mode?
Doesn't airo use "wifiX" for its monitor interfaces? For monitor
interfaces, should we adopt that convention as well?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-02-28 1:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 4:06 Patch to allow specification of interface name prefix Alex Davis
2007-02-25 4:30 ` Pavel Roskin
2007-02-25 4:39 ` Larry Finger
2007-02-26 23:02 ` Stephen Hemminger
2007-02-27 1:33 ` John W. Linville
2007-02-27 10:16 ` Jiri Benc
2007-02-27 17:41 ` Stephen Hemminger
2007-02-27 18:21 ` Ben Greear
2007-02-27 18:52 ` Pavel Roskin
2007-02-27 19:15 ` Johannes Berg
2007-02-27 18:55 ` Luis R. Rodriguez
2007-02-28 1:25 ` John W. Linville [this message]
2007-02-28 8:51 ` Johannes Berg
2007-02-28 16:44 ` Jouni Malinen
2007-02-28 16:50 ` Johannes Berg
2007-02-28 16:54 ` Luis R. Rodriguez
2007-02-28 16:55 ` Jouni Malinen
2007-02-28 18:35 ` John W. Linville
2007-02-28 19:21 ` Jouni Malinen
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=20070228012500.GB4072@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=alex14641@yahoo.com \
--cc=jbenc@suse.cz \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.org \
--cc=shemminger@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).