From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] Squashfs: Add support for LZMA compressed filesystems
Date: Sun, 13 Dec 2009 02:18:18 +0200 [thread overview]
Message-ID: <4B2432CA.1090800@pardus.org.tr> (raw)
In-Reply-To: <20091212052922.GB31742@wolff.to>
Bruno Wolff III wrote:
> On Mon, Dec 07, 2009 at 08:37:48 +0000,
> Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
>
>> Hi,
>>
>> The following patches add LZMA decompression support to Squashfs, using the
>> in-kernel LZMA decompression library.
>>
>
> I am a member of the Spins SIG and the Games Spin maintainer for Fedora.
> Thanks for working to get LZMA squashfs included in 2.6.33. If this
> gets accepted, we will have livecd-creator using it in F13 in order
> to include more packages in size limited images (such as the Games Spin)
> or reduce the size other images
>
Similar, I was looking forward to squashfs-lzma to use it on our
distribution's installation/live medium. I once digged into the openwrt
patches and failed. Now I tested your patches (on top of 2.6.30.9) +
userspace from CVS patched with lzma 4.65, it's working flawlessly. With
lzma, our live cd image's size decreased from 820mb to 692mb.
Thanks a lot for your work
Ozan Caglayan
next prev parent reply other threads:[~2009-12-13 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 8:37 [PATCH 0/9] Squashfs: Add support for LZMA compressed filesystems Phillip Lougher
2009-12-12 5:29 ` Bruno Wolff III
2009-12-13 0:18 ` Ozan Çağlayan [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-12-07 8:25 root
2009-12-07 8:47 ` Peter Korsgaard
2009-12-08 17:59 ` Phillip Lougher
2009-12-13 20:13 ` Arkadiusz Miśkiewicz
2009-12-13 20:13 ` Arkadiusz Miśkiewicz
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=4B2432CA.1090800@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/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.