Re: [patch] Support Debian's resolvconf

2005-08-01 Thread Colin Walters
On Sun, 2005-07-31 at 15:15 +0200, Olivier Blin wrote: Ok, but you could have enhanced the current system to have this kind of status reporting. Currently, I guess you have lost the ability to manage ppp connections, dsl connections and isdn connections in NetworkManager. I think a big

Re: [patch] Support Debian's resolvconf

2005-08-01 Thread Colin Walters
On Sat, 2005-07-30 at 14:38 -0400, Will Dyson wrote: On 7/28/05, Steev [EMAIL PROTECTED] wrote: Will Dyson wrote: I can work on moving the resolv.conf management into the backends, if people think that would be useful. Do any other distributions (or any of the BSDs) have their own

Re: [patch] Support Debian's resolvconf

2005-08-01 Thread Olivier Blin
Colin Walters [EMAIL PROTECTED] writes: For example, making 802.11 work really well, and not including ppp and idsn. I know ppp/isdn are probably very important to some people, but in good design you have to make some trade-offs. Well, you want NetworkManager to be *the* universal network

Braindump on wpa_supplicant

2005-08-01 Thread Dan Williams
Hi, So sitting in the airport at 10:30 at night last week I took a look at wpa_supplicant again. Again I've flip-flopped, I'm thinking that making a slave mode may be the best choice, but there are some utter stupidities in wpa_supplicant that make it a difficult. First, wpa_supplicant has a

Re: Braindump on wpa_supplicant

2005-08-01 Thread Olivier Blin
Dan Williams [EMAIL PROTECTED] writes: We could rely on wpa_supplicant to do scanning for us (or, perhaps, only when we ask it to scan) and then read the scan data from wpa_supplicant on a per-interface basis. It looks like a good plan! That's how I proceed in Mandriva tools to get

Re: Braindump on wpa_supplicant

2005-08-01 Thread Dan Williams
On Mon, 1 Aug 2005, Olivier Blin wrote: Dan Williams [EMAIL PROTECTED] writes: We could rely on wpa_supplicant to do scanning for us (or, perhaps, only when we ask it to scan) and then read the scan data from wpa_supplicant on a per-interface basis. It looks like a good plan!