From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-embedded@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, tim.bird@am.sony.com,
linux-next@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH V2 00/16] Squashfs: compressed read-only filesystem
Date: Sun, 4 Jan 2009 20:04:49 +0100 [thread overview]
Message-ID: <c384c5ea0901041104m31363264qd17d0181865c276@mail.gmail.com> (raw)
In-Reply-To: <49606B7C.7050403@lougher.demon.co.uk>
Hello,
On Sun, Jan 4, 2009 at 8:55 AM, Phillip Lougher
<phillip@lougher.demon.co.uk> wrote:
>> - what are the limitations of squashfs (please add this to the
>> changelog of patch #1 or something). Does it support nfsd? (yes, it
>> does!) xatrs and acls? File size limits, entries-per-directory,
>> etc, etc?
>
> Xattrs and acls are not supported, this is a todo.
> Filesize limits are in theory 2^64. In practice about 2 TiB.
>
...
>
> Ok. I'll re-spin the patches against 2.6.28 tomorrow (Sunday), and I'll
> prepare a tree for linux-next.
>
For use cases such as embedded firmware, the limitations are
non-interesting, and the compression savings are very interesting.
Especially where the resulting filesystem has to creep through slow
wires such as half duplex serial links etc.
Have been using squashfs 2.2 up to 3.4 without problems for years, for
distribution of Linux based firmwares into embedded devices.
Many thanks for your continued efforts on mainlining squashfs,
Regards,
--
Leon
next prev parent reply other threads:[~2009-01-04 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 1:49 [PATCH V2 00/16] Squashfs: compressed read-only filesystem Phillip Lougher
2008-10-29 2:29 ` Andrew Morton
2009-01-04 7:55 ` Phillip Lougher
2009-01-04 19:04 ` Leon Woestenberg [this message]
2008-10-29 21:39 ` Matt Mackall
2008-10-31 0:29 ` Phillip Lougher
2008-11-03 14:14 ` Evgeniy Polyakov
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=c384c5ea0901041104m31363264qd17d0181865c276@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).