[NTLUG:Discuss] Troubleshooting a network connection - fixed

[Chris Cox]

Terry Henderson wrote:
> On 5/11/06, Chris Cox <cjcox at acm.org> wrote:
>> Terry Henderson wrote:
>>> On 5/11/06, Terry Henderson <trryhend at gmail.com> wrote:
>>>> On 5/11/06, Chris Cox <cjcox at acm.org> wrote:
>>>>> Terry Henderson wrote:
>>>>>> Couldn't you have just swapped the cables?
>>>>> Hee hee... nope.  Unless you deploy named interfaces, the
>>>>> names can dynamically swap based on many, many, many, many
>>>>> different variables.
>>>>>
>>>>> That's a SUSE thing of course.. victims of a hotplug
>>>>> world.
>>>> Turn hotplug off.
>>> (For those that can not find a GUI menu for tuning hotplug off, just
>>> remove the executible bit for the simlink that points to hotplug,
>>> "chmod -x  /etc/rc.d/rc.wherever-it-is")
>> Turning off hotplug is sort of a knee jerk thing to do... I think
>> it's better to work with the OS rather than chopping it off
>> at the knees... just my opinion.
> 
> I don't see that it would hurt anything to turn off hotplug when your
> not using it. If you think it's causing problems, by all means, turn
> it off until you need it again. If you're not planning on adding any
> hardware that it needs to detect, then I see no reason to have it run
> each time you boot up.  Besides, your computer will boot faster if you
> turn it off.
> It can easily be turned it back on at any time, it only takes a couple
> seconds to turn it back on, so.... no big deal there. Right?
> 

Ok... whatever.  If there's a means of solving the problem without
going to extremes, I think it's a better route.. that's all.

I mean.. the whole point of "hotplug" is to NOT have to execute
some kind of command to see the device... :)