public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian Ludwig" <cl81@gmx.net>
To: "Tom Oehser" <tom@toms.net>
Cc: "Daniel Phillips" <phillips@arcor.de>,
	"Ville Herva" <vherva@niksula.hut.fi>,
	"Linux Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: [PATCH] bzip2 compression for kernel 2.4 and ramdisk
Date: Tue, 16 Jul 2002 10:28:15 +0200	[thread overview]
Message-ID: <002c01c22ca2$bb80a6d0$1c6fa8c0@hyper> (raw)
In-Reply-To: Pine.LNX.4.44.0207150807450.9793-100000@conn6m.toms.net

Hi,

I have released the new version 1.4 of the bzip2 support patch.
You can find it at http://chrissicool.piranho.com/linux (sorry for the ads.)

This patch consists actually of two independant parts, which do _not_ belong
together in any case. The only reason why they cannot be split up is that
both are using the same decompression code for bzip2 at the same location.
The two parts are:

1. A kernel bzip2 compression support patch.
The kernel will be compressed with bzip2, if you choose the appropriate
option in the "General options" menu of the kernel configuration. Choosing
gzip compression is still possible. You can also choose the compression
level in nine steps, from very poor compression (level 1), which is not very
memory and speed intensive. A very strong compression (level 9) makes the
bzImage smaller, but uses a large amount of RAM for decompression and takes
longer. This part is architecture dependent and was implemented for i386
based PCs.

2. A ramdisk bzip2 compression support patch.
You can enable gzip or bzip2 compression (or even both) for the ramdisk in
the kernel configuration. The ramdisk driver will test the image, which
should be loaded. If it recognises a valid (and supported) ramdisk image, it
will load and decompress it. The ramdisk compression is optional. You even
can turn off compressed ramdisk support at all.

If you find bugs, please mail me.

Have fun.

    - Christian Ludwig



  reply	other threads:[~2002-07-16  8:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 13:57 bzip2 support against 2.4.18 Christian Ludwig
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               ` Christian Ludwig [this message]
2002-07-13  5:16       ` 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='002c01c22ca2$bb80a6d0$1c6fa8c0@hyper' \
    --to=cl81@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --cc=tom@toms.net \
    --cc=vherva@niksula.hut.fi \
    /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