Le 03/05/2016 11:35, Daniel Reurich a écrit :
On 03/05/16 20:56, Didier Kryn wrote:
>Le 02/05/2016 03:41, Nate Bargmann a écrit :
>>I know, I would probably be better off doing everything it does by
>>hand. That said there is something very nice about opening the lid and
>>by the time I enter my password to unlock Xscreensaver, NM has the
>>network configured on my AP.
>
> FYI, this functionality is achieved by a proper configuration of
>wpa_supplicant.
>
> No need for an additional layer encumbered with so many dependencies.
>
You realise that NM uses wpa-supplicant right? It just doesn't do it
via the standard debian config files. We can fix the backend to do that
- but for now making it build to run without systemd is what we need.
:D
Yes, I know. All these front-ends use wpa_supplicant in their
kitchen. I just wonder why they find it more clever to re-do on their
own what wpa_supplicant can do alone.
However, IIUC, NM is also taking care of some usb connections,
which is out of the scope of wpa_supplicant.
Didier
_______________________________________________
Dng mailing list
[email protected]
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
