Do you know what piece of computer hardware is the most likely component to fail? If you answered the hard drive, you’re absolutely correct! Why? It’s one of the few moving parts left in a computer. With a hard drive, it’s not if it will fail, it’s when!
So, we know it’s going to fail. What can we do to:
Seems like most of my job now a days is looking at large systems and isolating problem areas. Things like performance problems, data corruption, or even failure analysis. Many of these systems have several independently managed processes, all tied together in a single forward facing application. Over the years, I’ve developed some methods of approaching system failures and problems that gives me a better chance of quickly evaluating and repairing the issues that plague these systems. I used to believe that these methods were only valid on larger system models, then, one day, a colleague of mine and I were sitting in a small coffee house discussing a problem they were having with one of the desktops they manage. While we exchanged ideas, I suddenly realized that I was using the same mental process on this little desktop as I did with the large cluster systems.
Some of the early groups of articles I penned on this blog, were comparisons of Open Source Groupware projects. At that time, the only one I could really recommend was eGroupware. Although I still believe eGroupware is a valid contender for your Groupware server, I have discovered a project, that in my opinion is leaps and bounds ahead of the pack. The project is called SOGo.
I thought I got this posted the beginning of the week, but I guess it slipped through the cracks… June 4, 2010, Adobe confirmed that a zero day exploit exists in it’s Flash Player, Acrobat and Adobe Reader software. This bug effects all of it’s supported platforms, and has been found in the wild.
So, you all know the drill, if your computer has the software listed in the Adobe Security Bulletin, then follow the instructions and get yourself safe!
This seems to be the cry of the hard core Linux and open source community in regards to the next release of Windows. Currently, most of the Linux camps are gearing up for all out war. Being a Linux and Open Source geek, I understand why we all seem to be bracing ourselves for a battle, but I think we might be going over the edge a bit on this one.
As my dad used to say, “Sometimes, the Dragon, he wins…”. For quite a while now, I have been on a mission to try to move my wife over to Open Office. She is a devoted Microsoft user, and runs the only jointly owned PC that has Windows as it’s primary operating system. Now, I’m not a totally anti-Microsoft, and I do believe that a person has the right to use whatever software they like, and are willing to properly license. But I really have a problem with paying for any software license when an equivalent Open Source option is available. I can’t seem to get through to my lovely wife, that Open Office will do all the things she uses MS Office for. The really sad thing, is she won’t even try Open Office. She gets mad if it’s on her PC! And when I ask her why she is against using it, she has the following reasons:
Looks like yet another change in KDE that messes with 3.5 users… Seems someone decided that the Autostart folder was a bad idea. This after having the Autostart folder in every KDE release I can remember.
Well, it seems that KDE 4 has adopted the same type of startup program control that Gnome has used for years.
A quick example.
Ok, let’s say that you want to start, oh I don’t know… Let’s say you want to start Krellm at login. here are the steps:
Well , that depends what you are looking for. My idea of a desktop might be a bit different from yours, and your idea might not mesh with your friends, or family. But if you are an average user, here are some things for you to think about.