As far as I'm concerned, dd is lower-level than most of the other utilities and provides more control over what's happening.
The author does have a point that the syntax is strange though.
As far as I'm concerned, dd is lower-level than most of the other utilities and provides more control over what's happening.
The author does have a point that the syntax is strange though.
Use noerror, but forget sync? Corrupt output file if there is an error. Use a bigger bs so it's not slow as treacle? A single faulty sector blows away a whole bs of data, and your output image may get unwanted padding appended to the end. Recoverable error? dd's not going to retry.
Use ddrescue or FreeBSD's recoverdisk(1). They're faster, they're safer, they're more effective, and they're easier to use.
[1]: http://www.gnu.org/software/ddrescue/ddrescue.html [2]: http://www.garloff.de/kurt/linux/ddrescue/
Funnily enough, I ended up using it to accidentally name the wrong drive in the argument, and lost years of photos, music, video etc. though I suppose I can't blame dd for that :)
I now use full paths for destination as well as source.