On Tue, Apr 25, 2006 at 09:36:57AM +0100, Digby Tarvin wrote:
>On Tue, Apr 25, 2006 at 08:15:07AM +0100, Magnus Therning wrote:
>> There is no problem, it has happened to others on the list. There was a
>> post on the list on solving it not so long ago.
>>
>> I solved it by having my wireless turn up as wlan0. For my card that's
>> controlled with an option to the driver. I just stuck the line
>>
>> options rt2500 ifname=wlan%d
>>
>> in a file in /etc/modprobe.d/. I'm not sure if other drivers support
>> doing the same.
>
>Thanks for the idea. I searched back through earlier posts, and don't
>know if it was the one you were referring to, but found the thread
>"load order of network interfaces" which led me to
> http://reactivated.net/writing_udev_rules.html#example-iface
>
>So I created a "/etc/udev/rules.d/10-local.rules" containing:
> KERNEL=="eth*", SYSFS{address}=="00:13:ce:b6:1c:fb", NAME="wlan0"
>
>which seems to implent the same sort of fix you used, but in a
>way that is independent of the available driver options.
Yes, that looks like what was mentioned earlier on the list :-)
I've followed you and put that line in a file in /etc/udev/rules.d/ as
well. Always nice to be independent of the driver in these cases.
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus@therning.org
http://therning.org/magnus
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.
Finagle's Sixth Law:
Don't believe in miracles -- rely on them.
Attachment:
pgpivOuH5PuOK.pgp
Description: PGP signature