mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Steven Noonan" <steven@uplinklabs.net>
Cc: "Bill Davidsen" <davidsen@tmr.com>,
	"Frans Meulenbroeks" <fransmeulenbroeks@gmail.com>,
	"Rob Landley" <rob@landley.net>, "Willy Tarreau" <w@1wt.eu>,
	"Alain Knaff" <alain@knaff.lu>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: bzip2 or lzma -compressed kernels and initrds
Date: Fri, 26 Sep 2008 20:53:09 +0200	[thread overview]
Message-ID: <c384c5ea0809261153t2c3a73c2sb46979962e8d1f8c@mail.gmail.com> (raw)
In-Reply-To: <f488382f0809151028w4b5b8a2bs86025e9286cfffe7@mail.gmail.com>

Hello all,

On Mon, Sep 15, 2008 at 7:28 PM, Steven Noonan <steven@uplinklabs.net> wrote:
> On Mon, Sep 15, 2008 at 10:13 AM, Bill Davidsen <davidsen@tmr.com> wrote:
>> Frans Meulenbroeks wrote:
>>>
>>> For kernel/ramfsimage etc the best choice is the one that has the
>>> fastest decompression (info on tukaani.org says gzip).
>>> Rationale: as it uncompresses faster the system will boot faster.
>>> ...
>
> It all really depends on what you're prioritizing.

Exactly.

Whenever LZMA comes up people start discussing the differences and
then discuss what is THE best.
So far, IMHO there is NONE. Selecting the best filesystem is about
making trade-offs depending on what you need.

For example, the systems I use squashfs for, are intended to be booted
only *once* (or incidently after a firmware upgrade). I do not care
about the memory it takes, or if takes twice as long. Also, I need the
rootfs to be read-only. Distributing over any media and uploading
Linux/FPGA firmware over very slow device backplanes is my main
concern.
Squashfs w/ LZMA works best for me, because smallest. Kudos.

Linux, THE best if you need choice.

Regards,
-- 
Leon

      reply	other threads:[~2008-09-26 18:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 21:19 Alain Knaff
2008-09-06 22:29 ` Leon Woestenberg
2008-09-06 22:59   ` Alain Knaff
2008-09-07  6:17     ` Rob Landley
2008-09-08  8:35       ` H. Peter Anvin
2008-09-08 13:14       ` Jörn Engel
2008-09-07  3:18 ` H. Peter Anvin
2008-09-07  4:35   ` Steven Noonan
2008-09-07  4:46     ` H. Peter Anvin
2008-09-07  7:40       ` Alain Knaff
2008-09-07 16:30         ` H. Peter Anvin
2008-09-07  7:39   ` Alain Knaff
2008-09-07  8:03     ` Yinghai Lu
2008-09-07  9:17       ` Alain Knaff
2008-09-07  5:48 ` Willy Tarreau
2008-09-07  8:59   ` Alain Knaff
2008-09-15  1:37   ` Rob Landley
2008-09-15 12:46     ` Frans Meulenbroeks
2008-09-15 17:13       ` Bill Davidsen
2008-09-15 17:28         ` Steven Noonan
2008-09-26 18:53           ` Leon Woestenberg [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=c384c5ea0809261153t2c3a73c2sb46979962e8d1f8c@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --cc=alain@knaff.lu \
    --cc=davidsen@tmr.com \
    --cc=fransmeulenbroeks@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=steven@uplinklabs.net \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®