[pkg-wpa-devel] Another note on wpa_gui and the new configuration scheme

[Felix Homann]

On Tuesday 18 April 2006 14:11, Reinhard Tartler wrote:
> On Mon, Apr 17, 2006 at 07:41:58PM +0200, Felix Homann wrote:
> > In this thread I tried to show you what doesn't work within the new
> > config scheme even if ifplugd is not involved.
>
> Sorry, this is getting silly. 

Yes, it is. But that's on your part.

> In this thread you are basically claiming 
> that wpa_gui was some sort of editor for wpa_supplicant.conf,

I'm just pointing out that it can be used as such.

> which 
> breaks when wpasupplicant is not started via an init script, 

Nowhere have I mentioned anything about an init script in this thread.

> and 
> therefore we must restore the init script to 'fix' wpa_gui.

I haven't said anything like that.

>
> Sorry, this argumentation is fundamentally flawed.

Yes, it is. I'm glad that it is your argumentation not mine.

> You make wrong 
> assumtions and (therefore) wrong conclusions.

Again, it's you.

>
> > Furthermore, I really think that wpa_gui is a very useful tool. It
> > might not be very complex but it does very well what it tries to do.
>
> It is useful, this is out of question. It is a tool to control a running
> supplicant using a graphical user interface. Nothing more.

Exactly.

> Ok. Thanks for the note. This is possible in the new setup as well, just
> let 'wpa-conf' point to an more or less empty configuration file, and
> add network blocks to it via wpa_gui, after ifupping the interface.
> Alternatively, you can start wpa_supplicant by hand as well.

Right. Now read my original mail in this thread again. That's exactly what I 
said. 

(As a hint for reading: By "daemon" I just mean a running wpa_supplicant 
process, similar to how the manpage uses this term. There's nothing 
indicating the use of an init script.) 

It just feels strange that you should (with an essentially empty 
wpa_supplicant.conf)  ifup an interface although you know it won't work 
because you haven't configured the wpa-related settings, yet. 

BTW, I've already suggested to use wpa_gui as an editor for the 
wpa_supplicant.conf even within the new scheme:

http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/2006-April/000249.html

> You don't seem to have much interest in this approach

At least I've got enough interest in the new approach to do a thorough 
testing. Remember, I even thought I could and would use it until I found the 
zeroconf issue. 

> but keep on 
> complaining about breaking older system 'without any reason'.

Sure, I've been complaining about breaking working setups on upgrade, but not 
in this thread. (But I'm still interested why you insist on breaking those 
setups. Actually, I know your reasons to create the new scheme, and I can 
agree whith most of _those_ reasons.)

Kind regards,

Felix