[CLUE-Tech] 20 Troubleshooting Tips for Mac, what about Linux?

[Nate Duehr]

On Tuesday 24 February 2004 09:03 pm, Kevin Cullis wrote:

> While yes, Zonker, I can search Google for info, but I was wondering if
> there is a simple yet logical flow of troubleshooting computer systems?
> While the link I posted was way over simplistic, I DO know that if you
> don't understand the concept level, you won't get the details, that's
> why they posted it as such.

I think the real problem is in making such a beast of a document is that the 
underlying technology is too flexible to realistically document in the 
limited time available.  We all love flexible software, but it results in 
hundreds of possible options/paths to go down in writing an all-encompassing 
troubleshooting document.  

This seems to be why "HOWTO" docs are more prevalent than good troubleshooting 
docs.  Step-by-step instructions to get from A to B seem much more reasonable 
to write with a few side-bars to explain other possible options for the 
reader to research on their own, then a monster all-seeing all-knowing 
document for when things are broken.

In addition, it just doesn't make economic sense.  Writing an all-encompassing 
document and trying to keep up with changes is far more 
time/resource-consuming than in learning to *be* logical about how one does 
troubleshooting.  ;-)

-- 
Nate Duehr, nate at natetech.com