Oliver Kurth <okurth@gmx.net> wrote:
> Naming wired network eth%d and wireless wlan%d would make things a lot
> easier. For example, it is easier to find out whether to start ifplugd
> or waproamd when the interface is created.
There's other (more resiliant) ways of doing that. In 2.6, wireless
cards will have a directory called wireless under sys/class/net/foo.
> I dislike naming wireless interfaces eth%d, because I often plug in a
> wired network card into my notebook at work, and a wireless card at
> home. They would both get eth1, but I may want different
> configurations.=20
But really, that's a problem that should be solved in a more generic
fashion. If I plug in two different wired cards, I'm probably doing so
because they've been left in two different places, and so want two
different configurations. But they'll both end up as eth2 anyway.
It makes more sense to either bind configuration to specific cards
(using the mac address, for instance), or different classes of card.
--
Matthew Garrett | mjg59-chiark.mail.debian.devel@srcf.ucam.org