GUI Wireless Tools

[Ed Fletcher]

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.
> 
> 
> On Sun, 13 Feb 2005 12:56:41 +1100, David Coldrick <coldrick at gmail.com> wrote:
> 
>>The reason I do that is simply that - at least when I tried it a
>>coupla months ago - startup got slowed down significantly by waiting
>>for non-existent network, which is a royal pain on a laptop.
>>
>>Regards,
>>David
>>
>>
>>On Fri, 11 Feb 2005 22:28:41 -0800, Ed Fletcher <ed at fletcher.ca> wrote:
>>
>>>David Coldrick wrote:
>>>
>>>>I currently run with networking not started, and i do a sudo ifup eth0
>>>>or sudo ifup wlan0 depending on my environment.
>>>>
>>>>Still trying to decide whete NetworkManager would be worthwhile for me
>>>>- installed it once and had a bunch of probs. and went back to the
>>>>usual.
>>>>
>>>>Do I need to configure network startup differently in order to use
>>>>NetworkManager?
>>>>
>>>>Regards,
>>>>David
>>>>

Ben:

I get the same problem as David, a very long boot up time when not on 
either a wired connection or using wireless at home.  And this predates 
the installation of NetworkManager, so that isn't the problem.  The boot 
process hangs for a while at the network stage.  Is that where you're 
doing the ctl-c?  And how do you know which process (wired or wireless) 
that you're killing?

Ed
-- 
Ed Fletcher
ed at fletcher.ca

What difference does it make to the dead, the orphans and the homeless,
whether the mad destruction is wrought under the name of totalitarianism
or the holy name of liberty or democracy?  -  Mahatma Gandhi (1869-1948)