Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread root
Package: wnpp
Severity: wishlist
Owner: Eun e...@su.am

* Package name: esu
  Version : 1.01
  Upstream Author : Eun e...@su.am
* URL : https://github.com/Eun/ecp
* License : GPLv3
  Programming Lang: C
  Description : It allows to copy files with different checksums on the fly.

Basicly a replacement for cp with additional checksum on the fly support.
It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512 algorithm to be used.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130820133306.14692.36296.report...@sd-27422.dedibox.fr



Re: Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread Ryan Kavanagh
On Tue, Aug 20, 2013 at 03:33:06PM +0200, root wrote:
 * Package name: esu
   Description : It allows to copy files with different checksums
 on the fly.
 
 Basicly a replacement for cp with additional checksum on the fly
 support.  It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512
 algorithm to be used.

How is this different from rsync? Quoting rsync(1):

   Rsync is a fast and extraordinarily versatile file  copying
   tool.   It can  copy  locally,  to/from  another  host  over
   any remote shell, or to/from a remote rsync daemon.
   [...]
   -c, --checksum  skip based on checksum,
   not mod-time  size

Best wishes,
Ryan

-- 
|_)|_/  Ryan Kavanagh   | Debian Developer
| \| \  http://ryanak.ca/   | GPG Key 4A11C97A


signature.asc
Description: Digital signature


Re: Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread Eun
The difference is that ecp generates the checksum on the fly, this means it
is faster then rsync,
rsync copy's first and compares the sum of the source and destination
afterwards (4 operations).
esu saves one operation by calculating the checksum during reading the file.

to make it clearer:

rsync:
1. read srcfile
2. write dstfile
3. checksum of src
4. checksum of dst

ecp:
1. read srcfile, checksum of src
2. write dstfile
3. checksum of dst



2013/8/20 Ryan Kavanagh r...@debian.org

 On Tue, Aug 20, 2013 at 03:33:06PM +0200, root wrote:
  * Package name: esu
Description : It allows to copy files with different checksums
  on the fly.
 
  Basicly a replacement for cp with additional checksum on the fly
  support.  It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512
  algorithm to be used.

 How is this different from rsync? Quoting rsync(1):

Rsync is a fast and extraordinarily versatile file  copying
tool.   It can  copy  locally,  to/from  another  host  over
any remote shell, or to/from a remote rsync daemon.
[...]
-c, --checksum  skip based on checksum,
not mod-time  size

 Best wishes,
 Ryan

 --
 |_)|_/  Ryan Kavanagh   | Debian Developer
 | \| \  http://ryanak.ca/   | GPG Key 4A11C97A



Re: Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread Konstantin Khomoutov
On Tue, 20 Aug 2013 10:21:05 -0400
Ryan Kavanagh r...@debian.org wrote:

 On Tue, Aug 20, 2013 at 03:33:06PM +0200, root wrote:
  * Package name: esu
Description : It allows to copy files with different checksums
  on the fly.
  
  Basicly a replacement for cp with additional checksum on the fly
  support.  It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512
  algorithm to be used.
 
 How is this different from rsync? Quoting rsync(1):
 
Rsync is a fast and extraordinarily versatile file  copying
tool.   It can  copy  locally,  to/from  another  host  over
any remote shell, or to/from a remote rsync daemon.
[...]
-c, --checksum  skip based on checksum,
not mod-time  size

It means do not copy a file if its checksum on the receiver is the
same as on the sender, that is, this option just modifies the way
`rsync` detects whether a particular file should be updated on the
receiver.  The proposed tool combines (unconditional) copying with
calculating a checksum over the copied content.  At least that's how I
read it.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130820184122.7d07669ce7812ad02d814...@domain007.com



Re: Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread Lars Wirzenius
On Tue, Aug 20, 2013 at 06:41:22PM +0400, Konstantin Khomoutov wrote:
 On Tue, 20 Aug 2013 10:21:05 -0400
 Ryan Kavanagh r...@debian.org wrote:
 
  On Tue, Aug 20, 2013 at 03:33:06PM +0200, root wrote:
   * Package name: esu
 Description : It allows to copy files with different checksums
   on the fly.
   
   Basicly a replacement for cp with additional checksum on the fly
   support.  It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512
   algorithm to be used.
  
  How is this different from rsync? Quoting rsync(1):
...
 [discussion of meaning of rsync option]

It would be helpful if the upstream README.md and the package description
explain what the checksums are for. Is this a replacement for cp+sha1sum
(or sha256sum or whatever algorithm is used), or is the checksum used
for verifying that the resulting file is copied correctly and has not
become corrupted during the copy? If the latter, does the program do
anything else to ensure a safe copy, such as fsync to make sure the
target file is committed to disk, or flushing kernel buffer caches so
that checksumming the target file happens on data that is read from the
target disk, and not from cache memory? Also an explanation of why this
is useful and why (and when) the kernel's usual mechanisms aren't enough
would be a good idea.

cp, but with checksums isn't a useful description of a program. Unless
the program's output includes the checksums (perhaps for later
verification), the checksums don't seem interesting to me as a user. They
seem like an implementation detail rather than an essential feature of
the program.

-- 
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130820150940.gg4...@mavolio.codethink.co.uk



Re: Bug#720327: ITP: esu -- It allows to copy files with different checksums on the fly.

2013-08-20 Thread Eun
Package name should be ecp, sorry misspelled that.

I fixed the README and improved some things.

Thanks for your feedback!


2013/8/20 Lars Wirzenius l...@liw.fi

 On Tue, Aug 20, 2013 at 06:41:22PM +0400, Konstantin Khomoutov wrote:
  On Tue, 20 Aug 2013 10:21:05 -0400
  Ryan Kavanagh r...@debian.org wrote:
 
   On Tue, Aug 20, 2013 at 03:33:06PM +0200, root wrote:
* Package name: esu
  Description : It allows to copy files with different checksums
on the fly.
   
Basicly a replacement for cp with additional checksum on the fly
support.  It allows MD5, SHA1, SHA224, SHA265, SHA384, SHA512
algorithm to be used.
  
   How is this different from rsync? Quoting rsync(1):
 ...
  [discussion of meaning of rsync option]

 It would be helpful if the upstream README.md and the package description
 explain what the checksums are for. Is this a replacement for cp+sha1sum
 (or sha256sum or whatever algorithm is used), or is the checksum used
 for verifying that the resulting file is copied correctly and has not
 become corrupted during the copy? If the latter, does the program do
 anything else to ensure a safe copy, such as fsync to make sure the
 target file is committed to disk, or flushing kernel buffer caches so
 that checksumming the target file happens on data that is read from the
 target disk, and not from cache memory? Also an explanation of why this
 is useful and why (and when) the kernel's usual mechanisms aren't enough
 would be a good idea.

 cp, but with checksums isn't a useful description of a program. Unless
 the program's output includes the checksums (perhaps for later
 verification), the checksums don't seem interesting to me as a user. They
 seem like an implementation detail rather than an essential feature of
 the program.

 --
 http://www.cafepress.com/trunktees -- geeky funny T-shirts
 http://gtdfh.branchable.com/ -- GTD for hackers