From: Jeff Garzik <jgarzik@pobox.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Phillip Lougher <phillip@lougher.demon.co.uk>,
Samuel Flory <sflory@rackable.com>,
linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: Squashfs released (a highly compressed filesystem)
Date: Tue, 29 Oct 2002 23:15:50 -0500 [thread overview]
Message-ID: <3DBF5CF6.3070103@pobox.com> (raw)
In-Reply-To: 20021029201110.A29661@work.bitmover.com
Larry McVoy wrote:
>>A r/w compressed filesystem would be darned useful too :)
>>
>>
>
>mmap(2) is, err, hard.
>
The underlying filesystem format can make things easier on you... and
given that compressing inevitably requires some amount of data copying,
it's not terribly difficult. I wouldn't claim NTFS is anything close to
well-designed, but supporting compression under Linux on NTFS is at
least feasible and shouldn't require tons of thought. (I've looked at
it when dicking around with NTFS-TNG)
> Not impossible, it means the file system has to
>support both compressed and uncompressed files, but it's interesting.
>
>
well, yeah... ;-)
Jeff
next prev parent reply other threads:[~2002-10-30 4:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 2:29 ANNOUNCEMENT: Squashfs released (a highly compressed filesystem) 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 [this message]
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
2002-10-31 4:08 ` Phillip Lougher
-- strict thread matches above, loose matches on Subject: below --
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=3DBF5CF6.3070103@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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