public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Leber <christian@leber.de>
To: Frank Sorenson <frank@tuxrocks.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/2] lzma support: lzma compressed kernel image
Date: Tue, 14 Jun 2005 12:31:35 +0200	[thread overview]
Message-ID: <20050614103135.GA4319@core.home> (raw)
In-Reply-To: <42AE3C91.4090904@tuxrocks.com>

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

> I think one or more of the following ought to happen:
> - - Modify the help text in the Kconfig option to show people how to
> obtain, compile, and install lzma (and warn them they'll need to install
> it).

How to obtain should be enough, i'll add it.

> - - 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.

> - - 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?


Christian Leber

-- 
http://www.nosoftwarepatents.com


  reply	other threads:[~2005-06-14 10:31 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 [this message]
2005-06-15 21:27       ` Frank Sorenson

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=20050614103135.GA4319@core.home \
    --to=christian@leber.de \
    --cc=akpm@osdl.org \
    --cc=frank@tuxrocks.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