mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: linux-embedded@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, phillip.lougher@gmail.com,
	tim.bird@am.sony.com
Subject: Re: [PATCH 0/9] Squashfs: Add support for LZMA compressed filesystems
Date: Tue, 08 Dec 2009 17:59:01 +0000	[thread overview]
Message-ID: <4B1E93E5.8090104@lougher.demon.co.uk> (raw)
In-Reply-To: <87tyw3p3vu.fsf@macbook.be.48ers.dk>

Peter Korsgaard wrote:
>>>>>> "root" == root  <root@lougher.demon.co.uk> writes:
> 
>  root> Hi,
>  root> The following patches add LZMA decompression support to Squashfs, using the
>  root> in-kernel LZMA decompression library.
> 
>  root> The patches also add a decompression framework to Squashfs.
>  root> This allows LZMA decompression to be added cleanly, and it allows
>  root> additional decompressors to be easily added in the future.
> 
>  root> To enable the in-kernel LZMA decompression code to be used by Squashfs,
>  root> there are two patches to the lzma code itself: one to make lzma available
>  root> to non-init code, and one to make lzma reentrant.  These are obviously
>  root> not restricted to Squashfs, but are needed by any non-init code that
>  root> may wish to use lzma compression.
> 
> Nice, do you also have an mksquashfs with lzma support?
> 

Yes, in Squashfs CVS (http://sourceforge.net/projects/squashfs/develop).
You'll need to edit the squashfs-tools Makefile to enable LZMA support.
The comments in the Makefile should, hopefully, explain how to
build LZMA support into Mksquashfs/Unsquashfs.

Once built-in, LZMA support can be specified using the -comp lzma option, i.e.

mksquashfs dir dir.img -comp lzma

Unsquashfs doesn't need any extra options, it automatically detects which
compression has been used.

You can tell which compression algorithms Mksquashfs/Unsquashfs support by
just typing the command on its own (i.e. mksquashfs, or unsquashfs).  The
(de-)compressors available are displayed at the end of the output.

Phillip







  reply	other threads:[~2009-12-08 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  8:25 root
2009-12-07  8:47 ` Peter Korsgaard
2009-12-08 17:59   ` Phillip Lougher [this message]
2009-12-13 20:13     ` Arkadiusz Miśkiewicz
2009-12-07  8:37 Phillip Lougher
2009-12-12  5:29 ` Bruno Wolff III
2009-12-13  0:18   ` Ozan Çağlayan
2009-12-21 23:16 ` Bruno Wolff III
2009-12-21 23:47   ` Phillip Lougher
2009-12-21 23:56     ` Bruno Wolff III
2009-12-31 12:06     ` Bruno Wolff III
2010-01-01  9:11       ` Bruno Wolff III

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=4B1E93E5.8090104@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=jacmet@sunsite.dk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip.lougher@gmail.com \
    --cc=tim.bird@am.sony.com \
    /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®