GUI Wireless Tools

[Dennis Kaarsemaker]

On Sat, 2005-02-12 at 21:50 -0500, Ben Novack wrote:
> The solution I use is starting both wired and wireless at startup, but
> hitting ctrl-c to kill the DHCP process on whichever one I don't want
> to use. It's ugly - I've love for it to 'just work' as cleanly as it
> does in Windows - but it gets the job done.

Why not start the dhcp client in the background? I start all network
related stuff (xsupplicant, wpa_supplicant, dhclient3) in the background
so booting does not take a long time.
-- 
Dennis K.
  And that's the way the cookie crumbles!