Update of /cvsroot/fink/dists/10.4/stable/main/finkinfo/10.4-EOL/utils
In directory vz-cvs-3.sog:/tmp/cvs-serv3383
Added Files:
ddrescue.info
Log Message:
sync. w/ 10.!4/stable, 10.4-EOL/unstable
--- NEW FILE: ddrescue.info ---
Package: ddrescue
# Version: 1.24
Version: 1.14
Revision: 1
BuildDepends: lzip
GCC: 4.0
# Source: http://www.garloff.de/kurt/linux/ddrescue/dd_rescue-%v.tar.gz
Source: http://download.savannah.gnu.org/releases/%n/%n-%v.tar.lz
# Source-MD5: f616e59ec31a667127d877b551b8d893
Source-MD5: 122d628c884a170659ac4c227cc484bc
# SourceDirectory: dd_rescue
SourceDirectory: .
PatchScript: lzip -d %n-%v.tar.lz && tar xvf %n-%v.tar && mv %n-%v/* .
ConfigureParams: --mandir=%p/share/man CXXFLAGS=-Os CPPFLAGS=-I%p/include
LDFLAGS=-L%p/lib
CompileScript: ./configure %c && make
InfoTest: TestScript: make -k check || exit 2
InstallScript: make install DESTDIR=%d
DocFiles: AUTHORS COPYING ChangeLog NEWS README
InfoDocs: ddrescue.info
License: GPL
Homepage: http://www.garloff.de/kurt/linux/ddrescue/
# Homepage: http://www.gnu.org/software/ddrescue/ddrescue.html
Maintainer: Jack Fink <[email protected]>
Description: Copies data between file/block devices
DescDetail: <<
GNU ddrescue is a data recovery tool. It copies data from one file
or block device (hard disc, cdrom, etc) to another, trying hard to
rescue data in case of read errors.
Ddrescue does not truncate the output file if not asked to. So,
every time you run it on the same output file, it tries to fill in the gaps.
The basic operation of ddrescue is fully automatic. That is, you don't
have to wait for an error, stop the program, read the log, run it in reverse
mode, etc.
If you use the logfile feature of ddrescue, the data is rescued very
efficiently (only the needed blocks are read). Also you can interrupt the
rescue at any time and resume it later at the same point.
Automatic merging of backups: If you have two or more damaged copies
of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with
the same output file, you will probably obtain a complete and error-free file.
This is so because the probability of having damaged areas at the same
places on different input files is very low. Using the logfile, only the needed
blocks are read from the second and successive copies.
The logfile is periodically saved to disc. So in case of a crash you can
resume the rescue with little recopying.
Also, the same logfile can be used for multiple commands that copy
different areas of the file, and for multiple recovery attempts over
different subsets.
Ddrescue aligns its I/O buffer to the sector size so that it can be used
to read from raw devices. For efficiency reasons, also aligns it to the
memory page size if page size is a multiple of sector size.
<<
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-commits mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.cvs
