Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment Downgrade (Score 1) 230

"This is yet another serious example of the need for us to upgrade and better safeguard our city's technology infrastructure," Rawlings said

This is an even better example of the need to downgrade. The sirens weren't always connected to the Internet. What compelling reason requires them to be connected to the Internet now?

Internet security lesson #1: if it doesn't need to be connected to the Internet, don't connect it to the Internet.

Comment no means no (Score 1) 3

I've been doing Linux development work for a quarter of a century and not once have I been asked to do it with Windows tools. The worst I've been asked is to use a Windows desktop with remote access to the Linux servers. The second worst was being asked to use the Linux client for the Windows-based version control system. Neither of these things was particularly bad.

If your employer is doing stupid things like demanding you do Linux work without administrative access to your development environment, find a new employer. Your current one won't change, he'll just fail. Why fail with him?

Comment Annotated (Score 1) 2

The key word here is "annotated". Malamud had and has the right to publish the actual text of Georgia law. The annotations explain the law and correlate it with judicial precedent. They are not the law itself thus can be copyrighted.

That having been said, the state's claim of copyright on the work it deems the official publication of the law is a double-edged sword that's likely to cut them as well.

Comment Re:bit rot (Score 3, Informative) 475

Bit-rot is an issue inherent to any storage medium

Here's a quick article which explains how hard disks use error correcting codes so that the user-level experience is no bit rot but rather many many read failures before even a single block of undetectably corrupted data. Next time you can know what you're talking about.

http://www.pcguide.com/ref/hdd...

Comment Re:bit rot (Score 4, Informative) 475

"ZFS isn't even a filesystem for this age" - WTF does that even mean?

It means that even back when FAT was a johnny come lately it already had greater market penetration than ZFS. With decades behind it and broad market penetration today, there's good reason to believe it won't vanish with the advent of the next development in filesystem architecture. ZFS is likely to be a blip on the radar, a pause before the next innovation. Not what you want for an archival format.

Bit-rot is an issue inherent to any storage medium

Bit rot, aka corrupted data, is not inherent to correctly operating hardware. As implemented, you'll see tens of thousands of unreadable blocks on a hard disk before you see a single one in which data has been undetectably corrupted. Every single sector gets a checksum in hardware and if the checksum does not pass you get the famous Abort Retry Ignore. For most storage you get Forward Error Correction coding so that some number of bit errors can be corrected on read before having to throw an error.

When you see bit rot, the storage media is usually not at fault. More often the data passes through faulty non-parity ram, a noisy memory bus or an overheated controller and gets corrupted on its way to storage rather than getting corrupted at rest on the storage. It died when you used an overclocked piece of garbage to copy it from an old hard disk to a newer, bigger one.

Comment Re:bit rot (Score 4, Informative) 475

He said a filesystem for the ages. While it has wonderful features, ZFS isn't even a filesystem for this age, let along ages to come. FAT32 and ISOFS are your best bets for being readable 20 years from now.

Bear in mind that your hard disk checksums each block and returns an error if the block is uncorrectable upon read rather than give you bad data. So, if you're getting bit rot at all then you have a hardware problem.

With or without a hardware problem you want to be able to recover your data. The answer is par2, such as parchive or QuickPar. Par2 uses a Reed-Solomon code to take a set of source files and produce a set of recovery files such that the original files can be checked for correctness and up to N original files can be corrected where N is the number of recovery files created.

And that's your answer. A filesystem like FAT32 or ISOFS that's likely to still be implemented in future OSes and a recovery files which let you rebuild anything that suffers from bit rot.

Slashdot Top Deals

Building translators is good clean fun. -- T. Cheatham

Working...