From: "Christian Ludwig" <cl81@gmx.net>
To: "Ville Herva" <vherva@niksula.hut.fi>
Cc: "Linux Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: bzip2 support against 2.4.18
Date: Thu, 11 Jul 2002 09:21:07 +0200 [thread overview]
Message-ID: <002601c228ab$86b235e0$1c6fa8c0@hyper> (raw)
In-Reply-To: 20020711062832.GU1548@niksula.cs.hut.fi
I actually did not mesásured how much smaller bz2bzImages are definitely.
Want to say that I haven't made a complete battery of tests yet.
The only thing I found out empirically is that my boot+root floppy (2MB
ext2fs root, totally overcrowded of course ;( and with kernel/ramdisk dd'ed
straight on it without lilo) is about 1.42MB with the standard 2.4.18 kernel
alltogether. Using bz2bzImage and compressing the root image with bzip -9
the overall size went down to 1.3MB with exactly the same configuration.
I also have tested it with a 4MB RAM 486DX-100 PC, but this crashed after
loading the kernel, so the decompression failed.
Putting in another 4MB into that machine (thus it has 8MB now), made the
kernel boot, but ramdisk decompression failed. All in all you will need at
least 12MB to boot correctly, if you are using a bz2bzImage of about 700kB
and a 2MB compressed ramdisk image.
But I think nowadays ram shouldn't be that problem anymore, as log as we are
speaking of 12MB. For anybody who does not have that "much" ram the old
method is still available...
Have fun...
- Christian
---------------------------------
Computers get faster every day.
Linux gets better every day.
I won't use Windows in no way.
next prev parent reply other threads:[~2002-07-11 7:17 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 ` Christian Ludwig [this message]
2002-07-11 17:22 ` bzip2 support against 2.4.18 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='002601c228ab$86b235e0$1c6fa8c0@hyper' \
--to=cl81@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--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