From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: [PATCH] optional use "gzip --rsyncable" for bzImage
Date: Wed, 16 Nov 2005 14:08:48 +0100 [thread overview]
Message-ID: <200511161408.49287.philipp.marek@bmlv.gv.at> (raw)
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?
Regards,
Phil
From: philipp.marek@bmlv.gv.at
diff -urN linux-2.6.12.orig/arch/i386/boot/compressed/Makefile linux-2.6.12/arch/i386/boot/compressed
/Makefile
--- 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
#
+ifdef CONFIG_RSYNCABLE
+GZIP_OPT := --rsyncable
+else
+GZIP_OPT :=
+endif
+
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.
+config RSYNCABLE
+ 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
next reply other threads:[~2005-11-16 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 13:08 Ph. Marek [this message]
2005-11-17 1:54 ` Andrew Morton
2005-11-19 0:34 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511161408.49287.philipp.marek@bmlv.gv.at \
--to=philipp.marek@bmlv.gv.at \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®