From: "Christian Ludwig" <cl81@gmx.net>
To: "Kernel.org" <linux-kernel@vger.kernel.org>
Subject: bzip2 support against 2.4.18
Date: Wed, 10 Jul 2002 15:57:27 +0200 [thread overview]
Message-ID: <003d01c22819$ba1818b0$1c6fa8c0@hyper> (raw)
Hey,
I think it's time to have bzip2 support in the kernel. I know the discussion
about the speed and memory issues that are around with this. But everything
in this patch is optional. You may use these new features if you want, you
do not have to use them...
This is a testing version of the patch. Only apply this if you really want
to play around with it a little bit. I know too less persons, who have the
time/fancy to test it (including myself). If you find errors in it feel free
to go on developing the patch yourself! Just CC a copy to me.
This patch consists actually of two parts:
1. A kernel bzip2 compression patch. The kernel will be compressed with
bzip. Therefore you have to type "make bz2bzImage" at the prompt after the
kernel configuration. This part is architecture dependent and was
implemented only for i386 based PCs right now.
2. A ramdisk bzip2 compression support patch. The ramdisk/initrd recongnises
now bzip2 compressed ramdisk images, loads and decompresses them. You can
choose between gzip and bzip2 (or even both) in the kernel configuration.
These two parts cannot be split up, because both are using the same
decompression code in "linux/lib/bzip2_inflate.c".
I have adapted this kernel hack by Tom Oehser (tom@toms.net). He wrote this
for kernel 2.2 and I ported it to 2.4.18 and cleaned up the code.
You will find the diff here:
http://chrissicool.piranho.com/patch-2.4.x-bzip2-i386
Known bugs:
- gzip crc support was corrupted in file "rd.c", function
"flush_window()"
[maybe it can be fixed, but time is money...]
- too less testing time was invested
Best regards,
- Christian
next reply other threads:[~2002-07-10 13:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 13:57 Christian Ludwig [this message]
2002-07-10 15:54 ` bzip2 patent status query jbradford
2002-07-10 16:48 ` Albert D. Cahalan
2002-07-10 17:37 ` jbradford
2002-07-10 17:08 ` Alan Cox
2002-07-10 17:26 ` Mark Mielke
2002-07-10 21:11 ` Rik van Riel
2002-07-12 7:04 ` Christian Ludwig
[not found] ` <20020711062832.GU1548@niksula.cs.hut.fi>
2002-07-11 7:21 ` bzip2 support against 2.4.18 Christian Ludwig
2002-07-11 17:22 ` Daniel Phillips
2002-07-12 6:36 ` Christian Ludwig
2002-07-12 7:30 ` Daniel Phillips
2002-07-12 8:32 ` Christian Ludwig
2002-07-12 8:52 ` Daniel Phillips
2002-07-12 10:12 ` Christian Ludwig
2002-07-12 12:01 ` jw schultz
2002-07-12 14:25 ` Tom Oehser
2002-07-12 14:49 ` Mark Mielke
2002-07-15 21:31 ` Horst von Brand
2002-07-16 12:01 ` Tom Oehser
2002-07-12 12:37 ` Thunder from the hill
2002-07-13 13:56 ` john slee
2002-07-13 14:04 ` Daniel Phillips
2002-07-13 15:02 ` Tomas Szepe
2002-07-13 14:44 ` Thunder from the hill
2002-07-12 12:33 ` Thunder from the hill
2002-07-12 13:05 ` jbradford
2002-07-12 13:24 ` Mark Mielke
2002-07-12 13:49 ` Christian Ludwig
2002-07-12 14:21 ` Tom Oehser
2002-07-15 6:28 ` Christian Ludwig
2002-07-15 12:17 ` Tom Oehser
2002-07-16 8:28 ` [PATCH] bzip2 compression for kernel 2.4 and ramdisk Christian Ludwig
2002-07-13 5:16 ` bzip2 support against 2.4.18 Mike Touloumtzis
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='003d01c22819$ba1818b0$1c6fa8c0@hyper' \
--to=cl81@gmx.net \
--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