Note that wpa_supplicant comes with dbus support now, which will get utilized by netcfg in the near future. When using the dbus interface, wpa_supplicant will get launched by dbus as system service as soon as it is requested.

this is obsolete? I don't use wireless.

http://archlinux.fecko.sk/en/wireless/

You can do automatic service for it so.

Having a rc.d script for wpa_supplicant is useless, as launching wpa_supplicant on its own without support applications won't give you a working network. netcfg, networkmanager and wicd use wpa_supplicant as its wireless backend when needed. The next netcfg version will even use it all of the time.

What do you need the script for? If you need wireless roaming, you should look into the net-auto-wireless mode of netcfg-git (hopefully to be released next week).

Earlier I used to use wpa_supplicant with /etc/rc.local starting without wicd, netcfg, networkmanager, and It was very useful for my purposes, because I used console that time, without netcfg, recently I've been using netcfg since I know it.

wpa-supplicant is dbus-activated these days, so having an init script isn't of much use.

okay, nice to hear that really, thanks.

Using that dbus interface doesn't make any sense, unless you want to reinvent the wheel. It was just added because networkmanager feels like it's cool to use dbus. netcfg has actually dropped all dbus-based code paths due to their lack of usefulness.

so what do we do next on this one?

My question was answered, maybe it can be closed.