From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: bzDisk compression Q; boot debug Q
Date: Thu, 14 Jun 2001 14:44:37 -0600 [thread overview]
Message-ID: <3B292235.D81F3637@idcomm.com> (raw)
In-Reply-To: <6B1DF6EEBA51D31182F200902740436802678F59@mail-in.comverse-in.com> <3B2869F9.D0AE17CB@idcomm.com> <3B28ADB3.7CE09FC3@internet-factory.de>
Holger Lubitz wrote:
>
> "D. Stimits" proclaimed:
> > down to 1.44 MB. But then it would also have to be self-extracting,
> > which complicates it, so I'm wondering how effective this current
> > compression is, and if a more bzip2-like system would be beneficial as
> > kernels get larger?
>
> bzip2 has pretty large memory requirements, consuming up to 8 MB in
> addition to the data being uncompressed.
> Although thats less of an issue now than it was some years ago, i still
> doubt that the kernel is going to be bzip2 compressed any time soon.
>
> if you're looking for better compression, you might want to examine upx
> (http://wildsau.idv.uni-linz.ac.at/mfx/upx.html). The kernel image
> compression is still experimental, but already usable. kernels tend to
> get ~100 K smaller compared to the usual gzip compressed bzImage.
Interesting stuff...and the license is non-commercial as well.
D. Stimits, stimits@idcomm.com
>
> Holger
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-06-14 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 21:39 bzDisk compression Q; boot debug Q Khachaturov, Vassilii
2001-06-14 7:38 ` D. Stimits
2001-06-14 12:27 ` Holger Lubitz
2001-06-14 20:44 ` D. Stimits [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 21:11 D. Stimits
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=3B292235.D81F3637@idcomm.com \
--to=stimits@idcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).