[PATCH] optional use "gzip --rsyncable" for bzImage

From: Ph. Marek
Date: Wed Nov 16 2005 - 08:08:48 EST

Hello everybody!

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.

The default is "N" to stay compatible with current behaviour.

I didn't find an entry in MAINTAINERS; and according to git a lot of people
touch arch/i386/Kconfig, so I just send to the l-k.

Andrew, how about an -mm inclusion? Or is the patch too small to warrant that?



From: philipp.marek@xxxxxxxxxx

diff -urN linux-2.6.12.orig/arch/i386/boot/compressed/Makefile linux-2.6.12/arch/i386/boot/compressed
--- linux-2.6.12.orig/arch/i386/boot/compressed/Makefile 2005-06-17 21:48:29.000000000 +0200
+++ linux-2.6.12/arch/i386/boot/compressed/Makefile 2005-11-16 13:44:34.000000000 +0100
@@ -4,6 +4,12 @@
# create a compressed vmlinux image from the original vmlinux

+GZIP_OPT := --rsyncable
targets := vmlinux vmlinux.bin vmlinux.bin.gz head.o misc.o piggy.o
EXTRA_AFLAGS := -traditional

@@ -17,7 +23,7 @@
$(call if_changed,objcopy)

$(obj)/vmlinux.bin.gz: $(obj)/vmlinux.bin FORCE
- $(call if_changed,gzip)
+ $(call if_changed,gzip $(CONFIG_RSYNCABLE))

LDFLAGS_piggy.o := -r --format binary --oformat elf32-i386 -T

diff -urN linux-2.6.12.orig/arch/i386/Kconfig linux-2.6.12/arch/i386/Kconfig
--- linux-2.6.12.orig/arch/i386/Kconfig 2005-06-17 21:48:29.000000000 +0200
+++ linux-2.6.12/arch/i386/Kconfig 2005-11-16 13:27:12.000000000 +0100
@@ -922,6 +922,17 @@
generate incorrect output with certain kernel constructs when
-mregparm=3 is used.

+ bool "Make bzImage better rsyncable (EXPERIMENTAL)"
+ depends on EXPERIMENTAL
+ default n
+ help
+ Compresses the kernel with "gzip --rsyncable". This makes the kernel
+ slightly larger (1-2%), but allows rsync to synchronize.
config SECCOMP
bool "Enable seccomp to safely compute untrusted bytecode"
depends on PROC_FS
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/