From: Larry Finger <larry.finger@lwfinger.net>
To: Pavel Roskin <proski@gnu.org>
Cc: Alex Davis <alex14641@yahoo.com>,
linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: Patch to allow specification of interface name prefix
Date: Sat, 24 Feb 2007 22:39:19 -0600 [thread overview]
Message-ID: <45E112F7.9090908@lwfinger.net> (raw)
In-Reply-To: <20070224233001.3ok4k0c00ksos4sw@webmail.spamcop.net>
Pavel Roskin wrote:
> Quoting Alex Davis <alex14641@yahoo.com>:
>
>> This patch will allow you to specify the interface name prefix of wireless
>> devices.
>>
>> On my machine, the wireless devices under the bcm43xx driver are named
>> 'ethx'; I
>> would really rather have them called 'wlanx', like bcm43xx-d80211 does.
>
> You can use ifrename from wireless tools. Use the option that checks the
> ethtool information.
>
> Jean has just released Wireless Tools 29-pre12, which can read symlinks in
> sysfs. That would allow renaming d80211 based network devices by checking the
> "driver" symlinks in sysfs. I asked Jean to do that with bcm43xx_d80211 in
> mind.
>
> It's not that I'm against your patch. I'm rather ambivalent. But I think using
> ifrename could reduce the need in kernel support for interface renaming.
NACK.
On my system (openSUSE 10.2), one sets the name in /etc/udev/rules.d/30-net_persistent_names.rule. I
feel that interface renaming is handled perfectly well in userland, and kernel support is not needed.
Larry
next prev parent reply other threads:[~2007-02-25 4:39 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 [this message]
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
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=45E112F7.9090908@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=alex14641@yahoo.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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 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.