From: Faidon Liambotis <paravoid@debian.org>
To: linux-wireless@vger.kernel.org
Cc: networkmanager-list@gnome.org
Subject: Re: ath5k and network manager
Date: Thu, 20 Sep 2007 18:50:48 +0300 [thread overview]
Message-ID: <46F296D8.3090704@debian.org> (raw)
In-Reply-To: <200709201511.23400.mb@bu3sch.de>
[CCing networkmanager mailing list]
Michael Buesch wrote:
> On Thursday 20 September 2007, Luis R. Rodriguez wrote:
>> On 9/20/07, Stephen Hemminger <shemminger-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote:
>>> Network manager doesn't seem to detect ath5k. Perhaps it is because
>>> it is name "ath0". I think device should follow the convention of using
>>> name "wifi0" rather than BSD convention of putting driver name in device name.
>> I couldn't agree anymore. But my ath5k kicks out a wlan%d name as with
>> any other mac80211 driver. Is yours coming out to ath%d ?
>
> Probably udev renames it.
IMHO, NetworkManager should cope with whatever name is assigned to a device.
AFAIK, device names are only "suggestions" by the drivers; the user may
rename the device name (either by "ip link set name", with ifrename or
with udev rules) to his liking, e.g. home.
Granted, seems a bit of an overkill to rename a device on a machine
where NetworkManager is in charge of the device but still, there is no
reason why it shouldn't be allowed.
Regards,
Faidon
next prev parent reply other threads:[~2007-09-20 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 4:40 ath5k and network manager Stephen Hemminger
2007-09-20 12:55 ` Luis R. Rodriguez
2007-09-20 13:11 ` Michael Buesch
2007-09-20 15:30 ` Stephen Hemminger
2007-09-20 15:34 ` Luis R. Rodriguez
2007-09-20 15:35 ` Stephen Hemminger
2007-09-20 15:38 ` Luis R. Rodriguez
2007-09-20 15:42 ` Tim Gardner
2007-09-20 15:50 ` Faidon Liambotis [this message]
2007-09-25 18:27 ` Dan Williams
2007-09-25 19:03 ` Stephen Hemminger
2007-09-20 15:51 ` Dan Williams
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=46F296D8.3090704@debian.org \
--to=paravoid@debian.org \
--cc=linux-wireless@vger.kernel.org \
--cc=networkmanager-list@gnome.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).