Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:bit rot (Score 1) 475

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.

Lzip and lziprecover can help you keep your data safe in the long term. (For the kind of data where it makes sense to use a lossless compressor, that is).

Comment Re:In my experience (Score 1) 229

That does NOT eliminate the need for good code design, actually, having a good design phase is absolutely crucial to this approach, since else your juniors have to design. That would be ... let's say sub-optimal.

Even more important than good code design is good data format design. No amount of good code can compensate for the defects in a bad format.

Comment NTFS performance (Score 1) 271

What, in your opinion, makes NTFS a pain in your ass?

For example performance with very large files.

Subject: Re: [Bug-ddrescue] ddrescue. NTFS-3g eating 100%. Solved by switching to ext3

I had a ddrescue imaging to a file on an ntfs partition (mounted with ntfs-3g) on a USB drive on Ubuntu 9.04 LiveCD. It was going slower and slower, although number of errors was not increasing. I tried all the ddrescue options I could find, but nothing helped - it was working for 5 days already and was slowing down so much so it would never end. By the time I stopped it it copied 112Gb out of 223Gb.
Then I noticed that ntfs-3g was eating 100% cpu. So, I created an ext3 partition on the same USB drive, copied my image file and log there and restarted ddrescue.
Boy! it finished in a couple of hours!

Comment Re:It is if the linker complains about not finding (Score 1) 219

getopt() is in the header <unistd.h>, which is in POSIX, not ANSI. POSIX facilities are not guaranteed to be present on W*nd?ws systems. It also handles only short options, not long options. For those, you have to use getopt_long() of <getopt.h>, which isn't even in POSIX.
You can also use Arg_parser and avoid all the portability problems of getopt_long.

Slashdot Top Deals

The best book on programming for the layman is "Alice in Wonderland"; but that's because it's the best book on anything for the layman.

Working...