News flows in a different direction

There’s a post by the ZDNet Technical Director, George Ou, talking about the recently found issues with the Core 2 Duo processor.  Rather, he’s talking about people’s opinions about it.

I’m not linking it because it necessarily has more information, as it’s already been covered here, but rather to show the difference in speed and depth that can be found between what more annoying people like to call old media (print magazines) and new media (this Digest).

Books and books

Here’s two slightly tangential things that involve DragonFly: The first is a thread about large (64-bit) file support in Apache, and how it is treated as a special case because of poor planning under Linux – it’s not a problem in BSD. This led to an excellent quote from an excellent book, “The Cuckoo’s Egg“, by Clifford Stoll:

“We’re watching someone who’s never used Berkeley Unix.” He sucked in his breath and whispered, “A heathen.”

Also, “_why” posted a question about checkpointing to the users@ list, for an issue that Matthew Dillon later fixed. I recall that this _why is the same fellow who wrote “Why’s (Poignant) Guide to Ruby“, a programming book that is unlike any other.

Potential processor problems

According to these reports from the OpenBSD-misc mailing list, Intel’s Core Duo is buggy, and upcoming features on Intel motherboards create a second running environment accessible even when your computer is off, both of which create security risks. (Thanks, Hasso Tepper)

Before anyone starts to hyperventilate, keep in mind: 1: this is a warning of potential problems, not an assessment of existing problems. 2: It’s an OpenBSD mailing list, which can be described as ‘adversarial’.