[pkg-wpa-devel] Proposal: Split the package
Kel Modderman
kelrin at tpg.com.au
Tue Apr 11 10:37:42 UTC 2006
Felix Homann wrote:
>
> 3. It would provide an easily maintainable upgrade path, i.e. those who have
> been using the old daemon still can without trouble. (BTW, has anything
> improved for them by the new approach? I think it only has caused trouble...)
>
I have had great feedback from many people for the alternative approach
that I brought to the table; ifupdown integration.
> That's presumably everyone who has been using wpasupplicant before, who is
>
> just interested in having a working setup as before.
>
Subjectively speaking, wpasupplicant never really "worked" for me before
now.
The ifupdown scripts are self contained and lay dormant unless you
activate them with the special commands in /e/n/i, therefore they can be
installed by default regardless.
The init script, as I understand it, really has its limitations:
* it can be used with only one interface as defined in its conffile
* it conflicts with new low-level services, such as network-manager,
because it is always active
* it was never intended to be used as the backbone of a "roaming
daemon solution" (in my opinion) but was just used that way out of
convenience
I have no objection to the daemon personally, but its deprecation was
discussed and decided upon before I arrived on the scene. So I will
leave this discussion open at least until Reinhard is involved, and
focus on addressing the issues with ifupdown integration and
documentation until then.
Thanks, Kel.
More information about the Pkg-wpa-devel
mailing list