Although it is not the purpose shred is supposed to serve, it comes close. Often it would be nice to be able to test low-level media thoroughly, before shipping them or putting them into production. shred could easily be adapted into read()ing after write()ing so the data is verified; since it randomized input, a hard disk could be thoroughly tested. I'm writing a patch for shred with the --verify option, so that data is also read, and shred bails out if there is a read() or write() error. Would such an addition be welcomed? Sean _______________________________________________ Bug-fileutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-fileutils
