Simple test, see below.

It would appear that the compressors sync rapidly despite an
insertion.  (The last five bytes differ; presumably a checksum.)

This bug report should therefore be closed.

Perhaps the gzip invocation used in constructing the kernel or ramdisk
images that engendered this report did not actually have this switch
enabled?
--
Barak A. Pearlmutter <[EMAIL PROTECTED]>
 Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www-bcl.cs.nuim.ie/~barak/

----------------------------------------------------------------

$ tar -cf Humor.tar -C ~/usr Humor

$ (echo -n x ; cat Humor.tar) > Humor.tarx

$ gzip             < Humor.tar  > Humor.tar.gz 
$ gzip             < Humor.tarx > Humor.tarx.gz
$ gzip --rsyncable < Humor.tar  > Humor.tar.gzr
$ gzip --rsyncable < Humor.tarx > Humor.tarx.gzr 

$ ls -l Humor.tar*

    -rw-rw-r--  1 barak barak 5806080 Dec 27 04:03 Humor.tar
    -rw-rw-r--  1 barak barak 5806081 Dec 27 04:04 Humor.tarx

    -rw-rw-r--  1 barak barak 2510805 Dec 27 04:04 Humor.tar.gz
    -rw-rw-r--  1 barak barak 2510806 Dec 27 04:05 Humor.tarx.gz

    -rw-rw-r--  1 barak barak 2536190 Dec 27 04:04 Humor.tar.gzr
    -rw-rw-r--  1 barak barak 2536186 Dec 27 04:05 Humor.tarx.gzr

$ cmp --verbose --ignore-initial=0:1 Humor.tar{,x} | wc -l

    0

$ cmp --ignore-initial=1000805:1000806  Humor.tar{,x}.gz

    Humor.tar.gz Humor.tarx.gz differ: char 1, line 1

$ cmp --verbose --ignore-initial=0:1 Humor.tar{,x}.gz | wc -l

    2500230

$ cmp --ignore-initial=4190:4186  Humor.tar{,x}.gzr

    Humor.tar.gzr Humor.tarx.gzr differ: char 2531993, line 9702

$ cmp --verbose --ignore-initial=4:0 Humor.tar{,x}.gzr | wc -l

    4130

$ cmp --verbose --ignore-initial=4:0 Humor.tar{,x}.gzr | tail

       4144   4  20
       4145   0 163
       4146   0 143
       4147 377 362
       4148 377  57
    2536179 170 313
    2536180 244 207
    2536181 320 342
    2536182  45  40
    2536183   0   1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to