Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment: Re:Fear of the West? (Score 1) 268

by edmudama (#49661663) Attached to: Russian Company Unveils Homegrown PC Chips

I was answering why they don't just invalidate the patents and copy a modern CPU, and the answer is that the patents aren't the reason they're hard to copy. Intel (and others) don't patent their most critical secrets.

I completely agree they have the technology to build older designs, which is just fine. They can then decide whether the investment to upgrade is worth it to them or not.

Comment: Re:What I want to know is (Score 1) 184

by edmudama (#49658617) Attached to: Enterprise SSDs, Powered Off, Potentially Lose Data In a Week

The chance is the same AFR of the rest of the product, but yes, it's very small.

Your worst case is that you cycle your SSD to 100% of its capability (which basically no user does anyway) inside a freezer, then put it on your dashboard as you park your black-on-black sports car in death valley for a 6 month hiking trip.

If you're not doing all 3 of those things simultaneously I wouldn't worry.

Comment: Re:Mamangement (Score 1) 290

by edmudama (#49410755) Attached to: Is This the Death of the Easter Egg?

I 100% support breaks, downtime, leisure activities, water cooler chats, beer at lunch, naps, etc. Sufficient rest is essential to productivity.

That being said, I think it's a bad idea to spend recharge time making changes to your company's production codebase to add an easter egg. Spend it outside of the office, where it's actually restful for your brain so that you're more effective at work when you return.

If you own your own company/app/whatever, then by all means make whatever choices you want.

Comment: Re:What about secure data erasure? (Score 1) 438

by edmudama (#48464639) Attached to: How Intel and Micron May Finally Kill the Hard Disk Drive

Erases can fail, but that's typically a gross failure in the peripheral circuitry and not a cell-level/array-level problem. It's no different than you being unable to erase your data if you have a mechanical failure on a rotation drive.

Your most likely "leakage" case is with a grown defect or a change in the flash translation layer, however, the specs are written so those old locations must be erased by a secure erase command. I know that based on NAND physics, if you do that erase, the data is gone and never coming back. IMO, there really aren't enough electrons in a charge well to reliably encode "additional" information about the prior state of a bit following an erase.

An NSA hack is always possible where they install rogue firmware on the drive that doesn't actually secure erase properly, but that kind of argument/speculation is outside the scope of my answer.

Dead? No excuse for laying off work.