Date: Wed, 16 Nov 2005 17:54:13 -0800
From: Andrew Morton <akpm@osdl.org>
To: "Ph. Marek" <philipp.marek@bmlv.gv.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] optional use "gzip --rsyncable" for bzImage
Message-Id: <20051116175413.208d27db.akpm@osdl.org>
In-Reply-To: <200511161408.49287.philipp.marek@bmlv.gv.at>
References: <200511161408.49287.philipp.marek@bmlv.gv.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1000
Lines: 21

"Ph. Marek" <philipp.marek@bmlv.gv.at> wrote:
>
>  As (at least in debian) gzip has the "--rsyncable" parameter included, 
>  I'd like to suggest this patch to (configurable) use this for bzImage creation.

I'd doubt if this works with a compressed a.out.  Most changes one would
make to a kernel at the source level will cause changes all over the
generated binary, so rsync will send the whole compressed file anyway.

For example, a few-byte change in size of a function will cause a huge
number of `call xxxxxxxx' opcodes to turn into `call xxxxxxxx+N'.

So I'll need some convincing.  But even if convinced, this seems like an
exceedingly obscure thing that not many people would be interested in.

echo `/usr/bin/gzip --rsyncable $*' > ~/bin/gzip ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/