On 2/15/07, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:
On 2/15/07, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2007-02-15 at 09:19 -0500, John W. Linville wrote: > > > P.S. Michael is, of course, right that the tool for users probably > > should not rely on python (or perl, et al). FWIW, I got the > > impression that Johannes's tool was meant to use in the short-run > > for developers...? > > Yes. The advantage is that you don't even need to recompile it for new > commands. And hey, maybe we can hack it up to generate the C code for > the real tool :P I think the tool we should rely on next should be based on wpa_supplicant/wpa_cli codebase. wpa_supplicant already handles wext, directly through ioclt(), but nevertheless it does call the right ioctls. As such, it doesn't depend on iwlib so distributions who decide to ditch iwconfig won't need a the old library and still get backward compatibility . Extending it to support nl80211 would benefit the wpa_supplicant codebase and we can take advantage and fork our own new utility out of it. How about calling it "iw" as ifconfig's replacement is called "ip" ?
Oh and also -- what we can do for the userspace tool is rely on the old wext ioctls for each call until the respective nl80211 interface to cfg80211 is added. We can move forward replacing the ioctls as we go with each release of this new tool. Luis - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
