Linux filesystem development
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: the compressed file attribute
Date: Thu, 29 Jan 2004 23:00:00 +0000	[thread overview]
Message-ID: <40199070.9040201@lougher.demon.co.uk> (raw)
In-Reply-To: <1075415709.2575.80.camel@patibmrh9>

Pat LaVarre wrote:
> Does one of the Linux fs, other than ntfs, already let me distinguish
> one file from another by a compressed attribute?  What I'm hoping to
> find is:

> Compressing all files is not the same thing.  I don't want the file
> system deciding for me which files to compress.
> 

AFAIK e2compr is the only filesystem that does this 
(http://e2compr.sourceforge.net).  It seems to be intermittently 
maintained and the latest patch appears to be for 2.4.17.

CRAMFS, Squashfs, zisofs are read-only filesystems (you imply you want a 
rw filesystem), and compress all files.  JFFS2 is a compressed 
read-write filesystem for flash, but again it compresses all files.

FiST was mentioned a while back on this email group, they have a gzipfs 
(http://www.filesystems.org), but it is unclear from the documentation 
whether all files are compressed.


Phillip




  reply	other threads:[~2004-01-29 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 22:35 the compressed file attribute Pat LaVarre
2004-01-29 23:00 ` Phillip Lougher [this message]
2004-01-30  3:30   ` Erez Zadok
2004-02-03  7:47   ` H. Peter Anvin
2004-01-29 23:26 ` Andreas Dilger
2004-01-30  7:33 ` Yury V. Umanets

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=40199070.9040201@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=p.lavarre@ieee.org \
    /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