All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yury V. Umanets" <umka@namesys.com>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: the compressed file attribute
Date: Fri, 30 Jan 2004 09:33:24 +0200	[thread overview]
Message-ID: <1075448004.1963.11.camel@firefly> (raw)
In-Reply-To: <1075415709.2575.80.camel@patibmrh9>

On Fri, 2004-01-30 at 00:35, 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:
> 
> Uncompressed files work same as always.
> 
> Compressed files appear to work same as always, but under the covers the
> data of the file occupies more or less space according to how
> compressible it is.  Random access within the file either sequentially
> rewrites all the file or else garbage collects and defragments.
> 
> I ask here because I think Google mostly points me to file systems that
> compress all files e.g. fs/cramfs/README Future Development doesn't
> mention this twist, e.g. `ls fs | egrep -i nw5` is empty, ...
> 
> Compressing all files is not the same thing.  I don't want the file
> system deciding for me which files to compress.
> 
> Pat LaVarre
Take a look onto reiser4. It has plugin based architecture and has so
called crypto-compress unix file plugin. 

Probably it is what you are looking for, though it is not stable yet...

> 
> 
> -
> 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
-- 
umka


      parent reply	other threads:[~2004-01-30  7:33 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
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 [this message]

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=1075448004.1963.11.camel@firefly \
    --to=umka@namesys.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.