From: Greg Farrel (greg at domain netsoc.tcd.ie)
Date: Sat 28 Sep 2002 - 21:19:03 IST
> it's a dumb solution. you're either solving the wrong problem or using
> the wrong solution. but if you would like to continue going down the
> wrong road here's the info you seem to want:
lol. you suggested it :)
What i would rather is a reply from soneone who hopefully has experience
with this situation and can suggest a simple solution. If not I can just
write a small program to rename the wireless devices in order.
cheers for the url.
> this ioctl will return an error if the device is either up or if
> the name already exists. i would imagine that it's easier to parse
> /proc/net/wireless then it will be to keep track of what names you've
> allocated, when to run your script and a host of other issues.
It's an issue for scripting, but I can handle that without great
diffuculty, where it's more valuable is on the admin side. If they're all
ethN someone will do something silly to the wrong interface. It's human
> note, a grep on the 2.4.18 source tree finds 0 hits for wlan%d, one
> hit for wvlan%d and 9 for eth%d (and it's only 9 because most drivers
> (including the wireless drivers) call alloc_netdev or init_netdev -
> both of which allocate ethN names).
I didnt say the kernel used wlanN. I said the best drivers do. If you
care to look into wireless networking a bit more you might stumble
across host_ap drivers, as this is for a high end project I intend to use
the best drivers suitable for the job. That doesnt automatically mean
they're in the kernel.
Besides, I dont really mind what any particular driver uses as its device
name (this is impressively off topic). I merely want a different (and
consistant) name for wireless as opposed to wired devices. That's a pretty
small request and I still havent heard a decent reason from you not to want it?
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:19:08 GMT