From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Phillip Lougher <phillip@lougher.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANN] Squashfs 3.0 released
Date: Fri, 17 Mar 2006 11:40:23 +0100 [thread overview]
Message-ID: <20060317104023.GA28927@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <B6C8687D-6543-42A1-9262-653C4D3C30B2@lougher.org.uk>
On Fri, 17 March 2006 00:45:42 +0000, Phillip Lougher wrote:
>
> Squashfs 3.0 has finally been released. Squashfs 3.0 is a major
> improvement to Squashfs, and it addresses most of the issues that
> that have been raised, particularly the 4GB filesystem and file
> limit. It can be obtained from the usual address http://
> squashfs.sourceforge.net. There is still some work to be done, in
> particular NFS support which I'll add as soon as I get time. After
> this I'll consider resubmitting patches to the LKML.
>
> From the changelog, the improvements are as follows:
>
> 1. Filesystems are no longer limited to 4 GB. In
> theory 2^64 or 4 exabytes is now supported.
>
> 2. Files are no longer limited to 4 GB. In theory the maximum
> file size is 4 exabytes.
>
> 3. Metadata (inode table and directory tables) are no longer
> restricted to 16 Mbytes.
>
> 4. Hardlinks are now suppported.
>
> 5. Nlink counts are now supported.
>
> 6. Readdir now returns '.' and '..' entries.
>
> 7. Special support for files larger than 256 MB has been
> added to
> the Squashfs kernel code for faster read access.
>
> 8. Inode numbers are now stored within the inode rather than
> being
> computed from inode location on disk (this is not so much an
> improvement, but a change forced by the previously listed
> improvements).
Nice list of improvements. The one still painfully missing is a
fixed-endianness disk format. Would have been a good time to make an
incompatible change and decide on one or the other.
Jörn
--
And spam is a useful source of entropy for /dev/random too!
-- Jasmine Strong
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-03-17 10:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 0:45 [ANN] Squashfs 3.0 released Phillip Lougher
[not found] ` <20060317010529.GB30801@schatzie.adilger.int>
2006-03-17 1:30 ` Phillip Lougher
2006-03-17 1:51 ` Samuel Masham
2006-03-17 10:40 ` Jörn Engel [this message]
2006-03-17 11:16 ` Phillip Lougher
2006-03-17 12:43 ` Jörn Engel
2006-03-17 16:00 ` Jeff Garzik
2006-03-17 17:04 ` Phillip Lougher
2006-03-17 17:25 ` Jeff Garzik
2006-03-17 20:39 ` Willy Tarreau
2006-03-19 1:38 ` Phillip Lougher
2006-03-19 1:42 ` Phillip Lougher
2006-03-19 16:32 ` Pavel Machek
2006-03-21 16:01 ` Phillip Lougher
[not found] ` <20060321161452.GG27946@ftp.linux.org.uk>
2006-03-21 19:08 ` Phillip Lougher
2006-03-21 19:11 ` Pavel Machek
2006-03-21 20:03 ` Phillip Lougher
2006-03-21 20:07 ` Al Viro
2006-03-21 22:01 ` Jan Engelhardt
2006-03-21 22:11 ` Jeff Garzik
2006-03-21 22:59 ` Al Viro
2006-03-21 20:15 ` Pavel Machek
2006-03-21 20:33 ` Al Viro
2006-03-21 21:28 ` Andreas Dilger
2006-03-21 23:24 ` Jörn Engel
2006-03-17 15:54 ` Xavier Bestel
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=20060317104023.GA28927@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.org.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox