From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: bzDisk compression Q; boot debug Q
Date: Thu, 14 Jun 2001 01:38:33 -0600 [thread overview]
Message-ID: <3B2869F9.D0AE17CB@idcomm.com> (raw)
In-Reply-To: <6B1DF6EEBA51D31182F200902740436802678F59@mail-in.comverse-in.com>
"Khachaturov, Vassilii" wrote:
>
> > Question 2, apparently ramdisk uses gzip compression; the name of the
> > kernel from make bzImage seems to maybe refer to bzip2 compression. Is
> > the kernel image using gzip or bzip2 compression for bzImage? Would
> bzImage stands for "big zImage" - this is a format invented for kernels that
> don't fit into zImage. bzip2 has nothing to do with it :)
Compression is one of those areas someone is always claiming to own a
part of, so it is a pain to deal with. But I still curious, how
effective is the compression that "big zImage" uses, compared to
something like bzip2? If the algorithm is the same as what gzip uses,
I'd imagine that some of my current 1.6 MB boot images could be brought
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?
D. Stimits, stimits@idcomm.com
next prev parent reply other threads:[~2001-06-14 7:37 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 [this message]
2001-06-14 12:27 ` Holger Lubitz
2001-06-14 20:44 ` D. Stimits
-- 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=3B2869F9.D0AE17CB@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