Really? Switching to text files would magically fix this??

This flaw is not related to how the registry is loaded and/or interpreted, actually it's not the fault of the registry at all - it's a kernel exploit. The mitigation is to tweak *permissions* on a couple of reg keys that should have been tightened up in the first place. It's akin to allowing SUID root on the sudoers file and a kernel vulnerability that allows $BAD_GUY to use that fact - it's not the file itself.

Whether the info is in a database of binary values or a database composed of text files laying around a hard disk is immaterial - the permissions to change said config info would have made this a non issue.

Yes, Microsoft have been idiots, but they are trying to clean up thier act. If you're going to dis them, dis them for missing the reg key permissions, not the registry itself - al much more valid argument.

Keith is already dead, his brain just don't know it yet. The D&R license is likely for him, I think.

The UI is simple and elegant - you need no help file in order to operate it. The DRM stops immediately after you pay for the book. If you take proper steps, it will be preserved for a very long time, with no worries as to whose digital format it's in. The device can work with the power of one candle. Printed and bound books are timeless.

That being said, I like electronic versions too - the speed at which they can be copied are unmatched, they go wherever you do fairly conveniently and can be updated very quickly. You can zoom in and make the text as big as you want. Annotation and quotation are a breeze.

The best of both worlds would be a hardcover book, with a sleeve on the inside cover that has a USB type device that you can get the contents digitally to whatever device you want. Hell - if Bluetooth gets cheap enough, you could get it wirelessly from the book itself.

Hey, a man can dream.

Achh, laddie, then the TSA will 'no where to be puttin' tha brrrrooom stick, righ' up yer kilt.

Snuffing it on facebook before your time is not much of an issue, as they explicitly don't disable the account's ability to actually log in. If you wake up one day to find out you're dead, you can still log in, and that provides a pretty decent avenue for contesting the claim.

And I'd rather not go into how I know.

Lemme guess - You're Jesus and after Your resurrection Facebook screwed you over?

This should be a holiday before Prog-Rammers get one. After all, we're left cleaning up the mess that these people make of our systems.

(Yeah yeah, I know - the endless recursive fork() was a typo, you need root to make your job easier, you need more CPU, the SAN sucks, etc. Give me your budget and I'll do something about all that, K? HTH, HAND.)

Yes, I'm trolling, but without us on the job the Prog-Rammers would be staring at a black or blue screen.

...and the answer is "Didn't you do a risk analysis of the provider you hosted your income bearing site with?".

Darwin, dude - if you didn't know that your provider was seriously at risk of being taken out by the feds due to the actions of whom you were sharing space with, then your stupid ass starves as does your family's. Just Darwin at work.

cut 'em in eighths and get the salt and tequila.

T, FTF Sam-I-AM.