supplicant

Under the hood Android just uses wpa_supplicant for connecting to WAPs.

«I use Linux at home with card X and it works great when I custom-configure wpa_supplicant» or «Just buy a MBP».

I ran ./configure && make and killed /usr/bin/wpa_supplicant, then used my copy and like magic, it started working.

I'm hoping Mantle is to OGL what Mir was to Wayland - not a supplicant, but a kick in the rear to get their act in gear.

And more importantly, almost no one wants to be a supplicant or an arrogant boss.

I was able to modify the wpa-supplicant so it could connect to the house wifi and be controlled from my PC, instead of using the crappy iOS client.

NetworkManager is wildly better than manually editing a wpa_supplicant file, and Windows/Macs have seen similar improvements.

Same here, I kind of never got NetworkManager to do any good, I just gave up, so mii-tool, dhcpcd, iwconfig, wpa_supplicant are well used tools, basically it works fine, when I actually have the drivers.

Here is my top 42, in order of usage: ls, cd, git, ssh, make, e, cat, veille, rm, wpa_supplicant, grep, evince, mv, x, dhclient, cp, echo, todo, mplayer, scp, man, mkdir, ack, pdflatex, apt-get, apt-cache, sed, less, feh, racket, gcc, wget, xrandr, bg, svn, pmount, for, gpg, halt, ping, tail, top.

I got sick of every upgrade breaking something in my system and then especially got sick of deciding between figuring out how to use wpa_supplicant and installing NetworkManager which screws up my network settings as soon as I plug in the Ethernet cable while I'm still on my wireless.