netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.co.intel.com>
Cc: netdev@oss.sgi.com
Subject: Device naming for wireless NICs...
Date: Thu, 11 Mar 2004 10:28:23 -0600	[thread overview]
Message-ID: <405093A7.90209@linux.co.intel.com> (raw)
In-Reply-To: <20040311031709.GC3782@jm.kir.nu>


If this topic been hashed a lot already, please let me know the keywords I might 
search for in the archives to find the threads.

I've had a few requests by users of the IPW2100 wireless driver to switch the 
default interface name to be wlanX vs. ethX.  In my prior searches through the 
wireless drivers in the 2.6.3 kernel tree, I couldn't find any that changed from 
the default.

I don't mind adding a module parameter to change the default name (if that is 
the standard practice), but thought I'd see what others thing rather than just 
going off and doing something random.

Is there a technical or ease of use reason switching away from ethX?  My 
thinking in keeping it eth was that it then represents a greater chance of "just 
working" with most networking scripts and utilities that may assume ethX is the 
interface name.

Thanks,
James

  reply	other threads:[~2004-03-11 16:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  2:35 [PATCH 2.6] Intersil Prism54 wireless driver Jean Tourrilhes
2004-03-04  2:37 ` Jeff Garzik
2004-03-04  2:49   ` Jean Tourrilhes
2004-03-10  3:24   ` Jean Tourrilhes
2004-03-10  7:12     ` Jeff Garzik
2004-03-10 17:21       ` Jean Tourrilhes
2004-03-10 16:55 ` Christoph Hellwig
2004-03-10 17:21   ` Jean Tourrilhes
2004-03-10 17:29     ` Christoph Hellwig
2004-03-10 17:29     ` Jeff Garzik
2004-03-10 17:52       ` Jean Tourrilhes
2004-03-10 17:58         ` Jeff Garzik
2004-03-10 23:37           ` James Ketrenos
2004-03-11  2:31             ` Jouni Malinen
2004-03-11  2:43               ` Jeff Garzik
2004-03-15 22:18                 ` Pavel Machek
2004-03-15 22:44                   ` Jeff Garzik
2004-03-15 22:55                   ` Jean Tourrilhes
2004-03-11  2:48           ` Jouni Malinen
2004-03-11  3:02             ` Jeff Garzik
2004-03-11  3:17               ` Jouni Malinen
2004-03-11 16:28                 ` James Ketrenos [this message]
2004-03-11 16:36                   ` Device naming for wireless NICs Tomasz Torcz
2004-03-11 16:54                   ` Matthew Galgoci
2004-03-11 18:25                     ` Jeff Garzik
2004-03-11 18:23                   ` Jeff Garzik
2004-03-12 10:30                     ` P
2004-03-10 18:07     ` [PATCH 2.6] Intersil Prism54 wireless driver Jeff Garzik
2004-03-11  2:21       ` Jouni Malinen
2004-03-10 22:17     ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2004-03-11 18:22 Device naming for wireless NICs Jean Tourrilhes
2004-03-11 19:33 ` Matthew Galgoci
2004-03-11 19:47   ` Jean Tourrilhes

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=405093A7.90209@linux.co.intel.com \
    --to=jketreno@linux.co.intel.com \
    --cc=netdev@oss.sgi.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 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).