[pkg-wpa-devel] Re: Bug#359814: wpasuppplicant fails for lo
Kel Modderman
kelrin at tpg.com.au
Wed Mar 29 21:28:20 UTC 2006
Reinhard Tartler wrote:
> On Wed, Mar 29, 2006 at 03:51:14PM +0200, Michael Biebl wrote:
>
>>> If you spot other issues, please tell us, we are considering to upload this
>>> integration to unstable soon.
>>>
>> /etc/default/wpasupplicant is missing (don't know if that's
>> intentional). /etc/wpasupplicant.conf was not migrated to
>> /etc/wpasupplicant/wpasupplicant.conf. Instead I have two files now.
>> Rather confusing since I don't know which of those two files I have to
>> edit. Simply move /etc/wpasupplicant.conf to the new location and if you
>> want to keep backwards compatibility, make a symlink.
>>
>
> Yes, we are currently working on sane upgrade paths and documentation
> for that.
>
I was thinking about moving to new location plus symlink also, but left
it open for now.
> The file /etc/wpa_supplicant/wpa_supplicant.conf is a simple example,
> which connects to all open APs. Since we don't use this file isn't used
> by default, I'd suggest moving it to
> /usr/share/doc/wpasupplicant/examples. Kel, Kyle, Daniel, do you agree with
> this suggestion?
>
>
And I really hate connecting to open ap's out of the box. Even worse, if
another network block is appended to the conf, without add priority=X,
the open networks will be connected to first, that sucks.
Additionally, moving that file out of conffile territory would get rid
of those pesky messages when installing new wpasupplicant packages,
prompting to overwrite a working, personal configuration file with a
generic one . . .
Thanks, Kel.
More information about the Pkg-wpa-devel
mailing list