Troubleshooting

From Arnout Engelen

[edit] Openness -> Better Troubleshooting

One of the main reasons I got involved in Linux and Open-Source, besides IT Efficiency, is because problems are solvable.

Of course, software should work correctly in the first place. However, software is so (sometimes inherently) complex that problems will arise - indeed, 'computer problems' are ubiquitous.

Most propriary software is presented as a black box: if it doesn't work, you're out of luck, and you're not allowed to look 'under the hood'. What drew me to Linux (in the broad sense of the word) was the fact that the Design of its components publicly available, and users with problems are actually invited to look 'under the hood', find out what exactly is the problem and fix it.

[edit] Information Overload

This advantage seems to be becoming less compelling.

Back in the days, if you had a problem with printing, you went looking for the Debian Manual and the LPD documentation. Today, where you need to look depends on many facors: are you using old-style LDP, CUPS or some other system, do you use KDE or Gnome, which distro is used, etcetera.

The information is still openly out there, but it has become much harder to find out what information applies to you, and where to look for it. We need to manage our information better.

[edit] Managing information

So this is the problem. Watch this space for rantings about solutions :).