[Forensics-changes] [safecopy] 01/01: New long description.

Joao Eriberto Mota Filho eriberto at moszumanska.debian.org
Thu Jun 25 18:18:38 UTC 2015


This is an automated email from the git hooks/post-receive script.

eriberto pushed a commit to branch debian
in repository safecopy.

commit c650be48b839a275d873dff476081177b9b17b22
Author: Joao Eriberto Mota Filho <eriberto at debian.org>
Date:   Thu Jun 25 15:18:09 2015 -0300

    New long description.
---
 debian/control | 40 ++++++++++++++++++----------------------
 1 file changed, 18 insertions(+), 22 deletions(-)

diff --git a/debian/control b/debian/control
index 8577594..b4f0f49 100644
--- a/debian/control
+++ b/debian/control
@@ -12,31 +12,27 @@ Vcs-Git: git://anonscm.debian.org/forensics/safecopy.git
 Package: safecopy
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: data recovery tool for problematic media
- Safecopy is a data recovery tool which tries to extract as much data as
- possible from a seekable, but problematic (i.e. damaged sectors) source.
+Description: data recovery tool for problematic or damaged media
+ Safecopy tries to get as much data from SOURCE as possible, even resorting
+ to device specific low level operations if applicable. This is achieved by
+ identifying problematic or damaged areas, skipping over them and continuing
+ reading afterwards. The corresponding area in the destination file is either
+ skipped (on initial creation that means padded with zeros) or deliberately
+ filled with a recognizable pattern to later find affected files on a corrupted
+ device. The work is similar to ddrescue, generating an image of the original
+ media. This media can be floppy disks, harddisk partitions, CDs, DVDs, tape
+ devices, where other tools like dd would fail due to I/O errors.
  .
- Safecopy works over every media, like floppy disks, harddisk partitions,
- CDs, DVDs, tape devices, where other tools like dd would fail due to I/O
- errors.
+ Safecopy uses an incremental algorithm to identify the exact beginning and
+ end of bad areas, allowing the user to trade minimum accesses to bad areas
+ for thorough data resurrection.
+ .
+ Multiple passes over the same file are possible, to first retrieve as much
+ data from a device as possible with minimum harm, and then trying to retrieve
+ some of the remaining data with increasingly aggressive read attempts.
  .
  Safecopy includes a low level I/O layer to read CDROM disks in raw mode,
  and issue device resets and other helpful low level operations on a number
  of other device classes.
  .
- Other Safecopy features are:
- .
-   - Can run from a previous or arbitrary position, and to keep trying to
-     open source files even when they went away. This allows copying from
-     devices that vanish temporarily in case of errors, like USB drives
-     that renumerate in case of device resets.
-   - Supports generic direct hardware access with O_DIRECT, as well as
-     reading from /dev/raw devices.
-   - DMA transfers to the read buffer are possible, bypassing CPU-based
-     in-memory copying by the kernel.
-   - Can generate a statistics file with the read timing information in
-     microseconds for each read block. This is useful for statistical
-     analysis of bad hardware behaviour and finding strategies to speed
-     up recovery tools like safecopy, ddrescue and the like.
- .
- Safecopy is useful in forensics investigations.
+ Safecopy is useful in forensics investigations and disaster recovery.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/forensics/safecopy.git



More information about the forensics-changes mailing list