Ira Abramov wrote:
[EMAIL PROTECTED] ~]$ tar icf - directory |md5sum
03ad652d93447a92eb944cd6acae0471 -
[EMAIL PROTECTED] ~]$ tar icf - directory |md5sum
03ad652d93447a92eb944cd6acae0471 -
[EMAIL PROTECTED] ~]$ tar icf - directory |md5sum
03ad652d93447a92eb944cd6acae0471 -
"i" for bzip2. still no surprise.
Well, one surpirse. "i" is not for bzip. If you want bzip, try "j".
however:
[EMAIL PROTECTED] ~]$ tar zcf - directory |md5sum
484497aa0d7e1bb391a73cc8b42acce2 -
[EMAIL PROTECTED] ~]$ tar zcf - directory |md5sum
552bbc02b0b2b5b142a425d476f0d5c0 -
[EMAIL PROTECTED] ~]$ tar zcf - directory |md5sum
792afdaf2be839dfccc1c91dfd4f726b -
what the fsck is going on?! is gzip adding some odd time stamp or
something?!
It appears so, yes:
ftp://ftp.isi.edu/in-notes/rfc1952.txt
MTIME (Modification TIME)
This gives the most recent modification time of the original
file being compressed. The time is in Unix format, i.e.,
seconds since 00:00:00 GMT, Jan. 1, 1970. (Note that this
may cause problems for MS-DOS and other systems that use
local rather than Universal time.) If the compressed data
did not come from a file, MTIME is set to the time at which
compression started. MTIME = 0 means no time stamp is
available.
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
