iftab is not working for me

[Ambrogio]

Il giorno mar, 27/06/2006 alle 22.17 +1000, Ben Stringer ha scritto:
> Hi Ambrogio,
> 
> The manpage for iftab recommends against using eth0, eth1 as interface
> names. 
> 
> <quote>
>  It is discouraged to try to map interfaces to default interfaces  names
>  such  as eth0, wlan0 or ppp0.  The kernel use those as the default name
>  for any new interface, therefore most likely an interface will  already
>  use this name and prevent ifrename to use it. Even if you use takeover,
>  the interface may already be up in some cases.  Not  using  those  name
>  will allow you to immediately spot unconfigured or new interfaces.
>  Good  names are either totally unique and meaningfull, such as mydsl or
>  privatehub, or use larger integer, such as eth5 or wlan5.   The  second
>  type is usually easier to integrate in various network utilities.
> </quote>
> 
> Perhaps the order of the interface discovery, and the use of ifrename in
> this way is leading to the inversion.
Well, I understood.
The problem is that iftab isn't the right way.
In my case is simple to change scripts to start networks, but I know
about some software that bind it's working IP address on first network.
So for example in my case, some agents are binded on wireless card.

There is a way to not load the wireless module at boot time, and to load
it only if I decide to start wireless network?

It seems that this problem is a big problem for a lot of people during
migration from 2.6.16 to 2.6.17.
For a lot of time it was enough to make change on modules.conf (and
after in modprobe.conf), but now it seems to be not enough.
Maybe a change in developer vision/idea, or maybe a not understood
enancement of feature, but it rest a problem in my opinion.

Bye
 Ambrogio