On Mon, Mar 12, 2007 at 10:21:49AM -0800, Jouni Malinen wrote: > On Mon, Mar 12, 2007 at 10:56:39AM -0700, Jean Tourrilhes wrote: > > > > I would guess that others "use" iwlib like that too. > > > > Which others ? The applications that process scan results can > > be counted on your fingers. And if you count the one actively > > developped, you can use one hand. > > Quick search of SIOCGIWSCAN with Google Code Search > (http://www.google.com/codesearch) shows quite large set of uses. Most > of them are from various drivers, but at least some (e.g., Xsupplicant, > waproamd) are from user space applications. I did not actually verify > whether any of these would be affected by the 64/32-bit issue, but I > would assume some of the apps are indeed parsing the scan results with > internal implementation. Note that you will get such a list on my web page, and if you find something not on the list, please send it to me. XSupplicant uses iwlib for scanning. waproamd has not been actively developped for the last 3 years. kdenetwork/KWiFiManager uses iwlib for scanning. Kifi uses iwlib and has not been actively developped for the last 2 years. ApRadar has not been actively developped for the last 3 years. SuSE netapplet is no longer on the net. wifi-radar parse the output of iwlist. Mandrake net_applet, from what I can gather, use wpa_supplicant. Ok, we are left with : wpa_supplicant use its own code. NetworkManager : partially use iwlib, use own code for scanning. > Jouni Malinen Jean - 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
