Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
dd_rhelp is a bash script that handles a very useful program written in C by
Kurt Garloff which is called dd_rescue, which roughly acts as the dd(1) command
with the characteristic to NOT stop when it falls on read/write errors. But
using it is quite time consuming. This is where dd_rhelp come to help.
In short, it'll use dd_rescue on your entire disc, but will try to gather the
maximum valid data before trying for ages on bad sectors. So if you leave
dd_rhelp work for infinite time, it'll have the same effect as a simple
dd_rescue. But because you might not have this infinite time (this could indeed
take really long in some cases...), dd_rhelp will jump over bad sectors and
rescue valid data. In the long run, it'll parse all your device with dd_rescue.
You can Ctrl-C it whenever you want, and rerun-it at will, it'll resume its job
as it depends on the log files dd_rescue creates.
