All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: Tomas M <tomas@slax.org>
Cc: Jan Engelhardt <jengelh@medozas.de>, Pavel Machek <pavel@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: LZMA compression algorithm in Kernel - any chance to allow it?
Date: Fri, 27 Jun 2008 10:15:39 -0400	[thread overview]
Message-ID: <1214576139.7698.13.camel@weaponx> (raw)
In-Reply-To: <4864F524.2070603@slax.org>

On Fri, 2008-06-27 at 16:11 +0200, Tomas M wrote:
> Jan Engelhardt wrote:
> > On Thursday 2008-06-26 22:17, Pavel Machek wrote:
> >>> If I (or anybody else) submit LZMA code for inclusion in kernel, would you ACCEPT IT ?? (assuming the code looks nice to you)
> >> You need some good reason why lzma should be in kernel... like 'cramfs
> >> can use it'...?
> > 
> > squashfs if at all.
> > 
> 
> Well anything can use lzma or any other compressions, not only squashfs.
> Squashfs is a great example, where you get 30% smaller filesystems compared to gzip.

JFFS2 has an framework for having multiple compression algorithms.
Adding LZMA to that wouldn't be difficult either.

josh


  reply	other threads:[~2008-06-27 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  7:56 LZMA compression algorithm in Kernel - any chance to allow it? Tomas M
2008-06-26 12:31 ` Jan Engelhardt
2008-06-26 13:37   ` Tomas M
2008-06-26 16:00     ` Stefan Richter
2008-06-26 20:17 ` Pavel Machek
2008-06-27 12:14   ` Tomas M
2008-06-27 12:20     ` Pavel Machek
2008-06-27 13:32   ` Jan Engelhardt
2008-06-27 14:11     ` Tomas M
2008-06-27 14:15       ` Josh Boyer [this message]
2008-07-01  6:37       ` Jan Engelhardt
     [not found] <fa.WuwHJZhCHgER6Pu+gn66zdRwVUg@ifi.uio.no>
2008-06-27  1:58 ` Robert Hancock

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=1214576139.7698.13.camel@weaponx \
    --to=jwboyer@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=tomas@slax.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.