[pkg-wpa-devel] What's wrong with the new configuration scheme, IMO

[Felix Homann]

On Wednesday 26 April 2006 23:11, Kel Modderman wrote:
> Alexandre Rossi wrote:
> > I don't personally think what Felix it trying to explain is 'noise'. A
> > completely agree with him.
>
> He has brought up some very good points indeed,

I completely agree with you in this point ;-)

> but also stated the same 
> point on many occasions;

Sure, since nothing has changed.

> wants the init script solution back.

That's plain wrong! Please, don't spread this sort of misinformation about me! 
Let me quote myself:

"Having the init script in examples/ is perfectly OK for new users!" [1]

I want you to care for people who are upgrading their systems.

> This bug  
> (#360387 <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360387>) has
> been tagged wontfix on the BTS and another project has been plotted to
> fill the void that this change made.

A problem is solved when the problem is solved - not when you've got an idea 
how to solve it.

> > The new setup
> > mixes up unrelated network layers in /e/n/i additionnaly to disable an
> > easy roaming ability.
>
> Then wireless-tools also suffers from this "problem"?

Yes, I think so. But that doesn't mean it is *very* bad to have those options 
available, e.g. I personally like the wireless-powerperiod option very much. 
Nevertheless, I don't think that those settings really belong in /e/n/i and 
using them should not be encouraged. 

As another example take the 'sens' option from wireless-tools. Setting it 
makes sense even without configuring the IP etc. but even while e.g. 
scanning. Having the option available in /e/n/i makes it easy to set it up in 
a place where it is useful but still does not provide its full power. 

People are lazy and so am I: I think it would be better to set power period, 
sens etc. from an init script, but I didn't write one since in most of my use 
cases it is sufficient to have them in /e/n/i. Without the availability of 
these options in /e/n/i I most probably would have written an init script for 
my machine.

> Of course. Help start a wifiroamd package or a package containing all
> the stuff and info required for the WIG setup.

Why a new package? It's all there! Maybe just include the link to Alexandre's 
page in the documentation. The packages should not be bundled in any way 
since they are useful on their own right: 

	- wpa_supplicant chooses and connects to an AP
	- ifplugd brings interfaces up when the cable is plugged in or a connection
	  to an AP is established
	- guessnet can be used to select a network profile

There's no miracle work involved in setting them up. Just install the 
packages, read the documentation if needed [*] and configure them for your 
needs.


Kind regards,

Felix


[*] I don't think reading the documentation is needed for ifplugd in most 
cases

[1]http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/2006-April/000329.html