From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Samuel Flory <sflory@rackable.com>, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: Squashfs released (a highly compressed filesystem)
Date: Wed, 30 Oct 2002 07:28:38 +0100 [thread overview]
Message-ID: <20021030072838.A628@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3DBF5756.2010702@lougher.demon.co.uk>; from phillip@lougher.demon.co.uk on Wed, Oct 30, 2002 at 03:51:50AM +0000
On Wed, Oct 30, 2002 at 03:51:50AM +0000, Phillip Lougher wrote:
> 4. Full 32 bit uids/guids are stored (4 bits stored in inode, uses a
> lookup table, to give 48 uids/16 gids). File sizes upto 2^32 are
> supported. Timestamp info is stored. Cramfs truncates uids to 16 bits,
> uids to 8 bits. Cramfs files sizes are upto 2^24. No timestamp info.
> Squashfs takes advantage of metadata compression to have more info with
> smaller metadata overhead.
Why limiting to 2GB? AFAIR you wanted to use a cramfs-like
filesystem for backups. Are videos and large data bases not worth
of backing up?
It seems to be good work. So I really wait for Al Viros comments ;-)
Regards
Ingo Oeser
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-10-30 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 2:29 Phillip Lougher
2002-10-30 3:10 ` Samuel Flory
2002-10-30 3:51 ` Phillip Lougher
2002-10-30 4:03 ` Jeff Garzik
2002-10-30 4:11 ` Larry McVoy
2002-10-30 4:15 ` Jeff Garzik
2002-10-30 14:53 ` Jesse Pollard
2002-10-30 15:10 ` Padraig Brady
2002-10-30 15:42 ` Denis RICHARD
2002-10-31 16:18 ` Nicholas Wourms
2002-10-30 23:56 ` Phillip Lougher
2002-11-01 15:57 ` Rob Landley
2002-11-02 8:57 ` Phillip Lougher
2002-10-30 6:28 ` Ingo Oeser [this message]
2002-10-31 4:08 ` Phillip Lougher
2002-10-30 14:17 Matthew Wilcox
2002-10-31 5:12 Phillip Lougher
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=20021030072838.A628@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=sflory@rackable.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®