View Single Post
Old 09-01-2012, 01:12 PM   #10
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,773
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Whether or not one believes thehawkman ought be concerned about whether calibre does or doesn't change checksums, there is an anomaly here.

If I rename or move or copy a file in Windows or Solaris the checksums don't change, and I'd bet London to brick on that Linux & OS/X are the same. The only things that change are the file modify date in the case of a rename or the create date in the case of a move or copy.

When I add a book to calibre I thought I was simply doing a copy and possibly a rename. However if I drop a 'new book' into calibre, I tested a PDF and a prc, the checksums of the book file change --- but if I copy a book from a Calibre library into another folder, and rename it and drop that book into another Calibre library the checksums of the book file don't change.

So why & what is it that calibre changes in data stream of a file the first time it sees the file - the file name is contained with the file system index and plays no part in computing checksums, which are computed from the file data fork/stream.

BR
BetterRed is online now   Reply With Quote