Getting people to use wpa_supplicant almost exclusivly as the interface for wireless will improve a lot of things. One thing that might help here is to do some work on the wpa_cli - to make it easier for the startup scripts to do what they need, and also to make the command syntax easier for command line users to do what they need.
Simon -----Original Message----- From: Dan Williams [mailto:[EMAIL PROTECTED] Sent: Thursday, October 26, 2006 8:33 AM To: Luis R. Rodriguez Cc: Johannes Berg; Michael Wu; Simon Barber; David Kimdon; netdev@vger.kernel.org; Jiri Benc; John W. Linville; Jean Tourrilhes; Hong Liu; Jouni Malinen Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211 On Thu, 2006-10-26 at 11:04 -0400, Luis R. Rodriguez wrote: > On 10/26/06, Dan Williams <[EMAIL PROTECTED]> wrote: > > While wpa_supplicant is certainly the main client for stuff directly > > related to setting up a connection, there are quite a few other > > users of general WE calls to pull information out of the card, or to > > receive scan events. > > How about we just ditch iwconfig completely and move on to > wpa_supplicant/wpa_cli as our next userspace application with > nl80211/cg80211 as our new API for usersapce-->kernel communication? > As you point out, wpa_supplicant already does a lot for us -- and > several distributions already rely on it. Some work is required but I > think its worth it. If we do a complete move from WE to nl80211 it > would be transparent to the users too. The one blocker I can think of here is startup scripts on various distributions. Most of those are shell, and they usually rely on iwconfig quite heavily. Getting those converted to wpa_supplicant wouldn't be a trivial amount of work, but it wouldn't be a ton either. Dan - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
