From: Frank Sorenson <frank@tuxrocks.com>
To: Christian Leber <christian@leber.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/2] lzma support: lzma compressed kernel image
Date: Wed, 15 Jun 2005 15:27:37 -0600 [thread overview]
Message-ID: <42B09D49.4090505@tuxrocks.com> (raw)
In-Reply-To: <20050614103135.GA4319@core.home>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Leber wrote:
> On Mon, Jun 13, 2005 at 08:10:25PM -0600, Frank Sorenson wrote:
>>patches appear to work as advertised.
>
> I don't like the moving of the initrd, but i don't know another way to
> get it working otherwise.
>
>>lzma reduced my kernel by
>>approximately 25%, so I'd say it looks promising.
>
> 25%? i would have expected a smaller saving
- -rw-r--r-- 1 root root 2959194 Jun 12 14:28 vmlinuz-2.6.12-rc6-fs1
- -rw-r--r-- 1 root root 2192674 Jun 13 21:47 vmlinuz-2.6.12-rc6-fs2
> How to obtain should be enough, i'll add it.
Great, thanks.
>>- - Detect that the lzma application isn't present, and fall back to gzip
>>(with a warning) if lzma fails.
>
> No.
> If you select lzma you have to have it, you also don't download a
> compiler when somebody tries to compile the kernel without a compiler.
Uhm, no, I wasn't saying that. Just suggesting a simple failsafe. It's not important.
>>- - If we can embed the decompressor into the boot-time kernel, can't we
>>put a compressor into the kernel source, and avoid the need for the
>>external program?
>
> How do think will people react to a hundreds of kb sized C++ patch that
> is not - i repeat - NOT in proper coding style?
I wasn't suggesting that we include the entire source code as-is. Just that if we can include the decompressor in < 45K of code, surely the compression could be included easily. Again, it's not very important. Giving enough information to build and run is most important.
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCsJ1JaI0dwg4A47wRAlu8AJ4svae4WhrMnZf8HRNJl0PBCsTaXACeIhIa
8rmljN+/ZG1Vtg5OPa5KSAc=
=rOJl
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-06-15 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 21:41 [PATCH 2/2] lzma support: lzma compressed kernel image Christian Leber
2005-06-12 22:31 ` Christian Leber
2005-06-13 4:25 ` Willy Tarreau
2005-06-14 2:10 ` Frank Sorenson
2005-06-14 10:31 ` Christian Leber
2005-06-15 21:27 ` Frank Sorenson [this message]
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=42B09D49.4090505@tuxrocks.com \
--to=frank@tuxrocks.com \
--cc=akpm@osdl.org \
--cc=christian@leber.de \
--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