As long as I am using Kopete, sending messages, etc. everything is as it should be. No connection problems at all. As soon as I let the program go idle, it starts disconnecting every ten minutes, giving an Error 17 message, like clockwork. It always reconnects on it’s own, but as you can see from the screenshot, you could set your watch by when it disconnects from the Yahoo server.

As a follow-up to Michael Stutz's excellent article, this article provides 10 more good habits to adopt that will improve your UNIX® command-line efficiency. Learn about common errors and how to overcome them, and discover exactly why these 10 UNIX habits are worth picking up!

Monitoring and analyzing performance is an important task for any sysadmin. Disk I/O bottlenecks can bring applications to a crawl. What is an IOP? Should I use SATA, SAS, or FC? How many spindles do I need? What RAID level should I use? Is my system read or write heavy? These are common questions for anyone embarking on an disk I/O analysis quest.

Adopt 10 good habits that improve your UNIX® command line efficiency -- and break away from bad usage patterns in the process. This article takes you step-by-step through several good, but too often neglected, techniques for command-line operations. Learn about common errors and how to overcome them, so you can learn exactly why these UNIX habits are worth picking up.

Here we go, bash scripting is nothing more then combining lots of UNIX commands
to do things for you, you can even make simple games in bash
(just UNIX commands) or as in normal cases, batch files to control things
in your computer.

In an attempt to find a good Unix reference for you FOSSwire readers, I was unsuccessful at finding a decent one on the Internet. So, why not make one?

SCO's new position is that UnixWare is just another interchangeable name for UNIX and that SCOsource was about UnixWare, not Unix System V, but here's some more evidence that they are not the same thing and that SCOsource was primarily about UNIX System V. In this article, I'll restrict myself to things SCOfolk used to say about what SCOsource was about. As you will see, before the Honorable Dale Kimball ruled in August that the UNIX copyrights didn't pass from Novell to SCO, SCO said SCOsource was about UNIX System V source code. Now that it's time to pay Novell for those System V licenses, SCO says they were really UnixWare licenses.

Linux (and indeed Unix) has long held the philosophy of "one tool for each job, and one job for each tool." This can lead to quite a paradox for newcomers to Linux: Why are there so many tools that do similar things?

One of the unsung heroes of the Unix realm is — I kid you not — IBM. Stop laughing, I'm serious.