Reader Patrick In Chicago is one of a few readers to write with this unpleasant news: “Computer-based testing provider Pearson Vue is now in day 5 of a global outage, preventing test-takers worldwide from sitting for exams. I was personally turned away from a Cisco exam on Wednesday morning because Pearson was unable to deliver. Countless people have posted to Pearson Vue’s Facebook page detailing various states of panic. There are people who have certifications expiring. Others are unable to sit their medical board exams. Still others are unable to sit exams that they are required to pass in order to work — Pearson Vue’s incompetence has actually prevented people from going out and making a paycheck.” This reminds me of a friend of mine who had to wait half a year to re-take his bar exam, because of a software glitch on the part of ExamSoft’s software. Read more of this story at Slashdot.
Read the original:
Pearson Vue Now On Day 5 of Massive Outage
An anonymous reader writes “Yesterday afternoon, Kaspersky Labs released a definition update that blocked all Internet and Intranet access on Windows XP workstations. While there has been no official communication from Kaspersky, their forum is lit up with angry customers relying on each other to find a fix.” Update: 02/05 16:42 GMT by T : Thanks to an anonymous reader, who says that Kaspersky has issued a statement, and a fix (though the fix takes some manual labor to implement). Read more of this story at Slashdot. 
An anonymous reader points out just how thick a skin it takes to be a kernel developer sometimes, linking to a chain of emails on the Linux Kernel Mailing List in which Linus lets loose on a kernel developer for introducing a change that breaks userspace apps (in this case, PulseAudio). “Shut up, Mauro. And I don’t _ever_ want to hear that kind of obvious garbage and idiocy from a kernel maintainer again. Seriously. I’d wait for Rafael’s patch to go through you, but I have another error report in my mailbox of all KDE media applications being broken by v3.8-rc1, and I bet it’s the same kernel bug. And you’ve shown yourself to not be competent in this issue, so I’ll apply it directly and immediately myself. WE DO NOT BREAK USERSPACE! Seriously. How hard is this rule to understand? We particularly don’t break user space with TOTAL CRAP. I’m angry, because your whole email was so _horribly_ wrong, and the patch that broke things was so obviously crap. … The fact that you then try to make *excuses* for breaking user space, and blaming some external program that *used* to work, is just shameful. It’s not how we work,” writes Linus, and that’s just the part we can print. Maybe it’s a good thing, but there’s certainly no handholding when it comes to changes to the heart of Linux. Read more of this story at Slashdot.