|To:||James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>|
|Subject:||Re: Device naming for wireless NICs...|
|From:||Jeff Garzik <jgarzik@xxxxxxxxx>|
|Date:||Thu, 11 Mar 2004 13:23:12 -0500|
|References:||<20040304023524.GA19453@xxxxxxxxxxxxxxxxxx> <20040310165548.A24693@xxxxxxxxxxxxx> <20040310172114.GA8867@xxxxxxxxxxxxxxxxxx> <404F5097.4040406@xxxxxxxxx> <20040310175200.GA9531@xxxxxxxxxxxxxxxxxx> <404F5744.1040201@xxxxxxxxx> <20040311024816.GC3738@xxxxxxxxx> <404FD6BC.7090409@xxxxxxxxx> <20040311031709.GC3782@xxxxxxxxx> <405093A7.90209@xxxxxxxxxxxxxxxxxx>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703|
James Ketrenos wrote:
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 lean towards wlan%d, but until we have the generic 802.11 stack going it's really up to the driver maintainer (you, in this case).
Like Matthew said, any code that assumes a specific interface prefix, be it eth%d or wlan%d, is buggy. Users are allowed to choose random interface names for their interfaces, often via nameif(8) program. My own ethtool program is broken in this regard...
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Device naming for wireless NICs..., Jean Tourrilhes|
|Next by Date:||Re: Device naming for wireless NICs..., Jeff Garzik|
|Previous by Thread:||Re: Device naming for wireless NICs..., Jeff Garzik|
|Next by Thread:||Re: Device naming for wireless NICs..., P|
|Indexes:||[Date] [Thread] [Top] [All Lists]|