public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lee Trager" <lt73@cs.drexel.edu>
To: linux-btrfs@vger.kernel.org
Subject: Selective Compression/Encryption
Date: Tue, 9 Dec 2008 09:59:52 -0500	[thread overview]
Message-ID: <20081209145952.GA30494@tux64-03> (raw)

Currently compression and I assume if encryption is implemented it is
turned on or off during mount. There are however many times when a user may
want to select which files/directories they want to compress or encrypt.
This will also be helpful when implementing btrfs support in grub for
example. We can say the disk can be compressed/encrypted except for /boot so 
compression/encryption doesn't have to be implemented in grub.

I was thinking of adding this functionality to the userspace application
btrfstune. The way I was thinking of doing this is when btrfstune +c is
applied to a directory or file the directory(and all its contents) or
file will always be compressed reguardless of how the filesystem is
mounted. The opposite would happen when btrfstune -c is used.

Would this be a reasonable thing to implement? Any suggestions before I
start doing this?

Lee

             reply	other threads:[~2008-12-09 14:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09 14:59 Lee Trager [this message]
2008-12-09 15:45 ` Selective Compression/Encryption Miguel Figueiredo Mascarenhas Sousa Filipe
     [not found]   ` <200812091722.21567.mail@earthworm.de>
2008-12-09 18:09     ` Lee Trager
2008-12-09 22:14       ` Miguel Figueiredo Mascarenhas Sousa Filipe
     [not found]         ` <1228863790.8130.14.camel@mattos-laptop>
2008-12-10 12:11           ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 23:05       ` Diego Calleja
2008-12-09 23:50         ` jim owens
2008-12-10  0:03           ` calin
2008-12-10 13:44           ` Chris Mason
2008-12-10 17:55             ` Christoph Hellwig
2008-12-10 18:02               ` Linda Knippers
2008-12-10 18:11             ` Joshua J. Berry
2008-12-10  9:06         ` Mattos, Oliver
2008-12-10  9:32   ` Jeremy Sanders
2008-12-10 12:19     ` Miguel Figueiredo Mascarenhas Sousa Filipe
2008-12-09 16:35 ` Chris Mason
2008-12-09 18:14   ` Lee Trager
2008-12-09 19:26   ` Joshua J. Berry
2008-12-09 20:22     ` jim owens
2008-12-10 13:45       ` Chris Mason
2008-12-10 14:33         ` btrfs with selinux jim owens
2008-12-11 22:03       ` Selective Compression/Encryption Lee Trager
2008-12-12 14:19         ` Chris Mason

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=20081209145952.GA30494@tux64-03 \
    --to=lt73@cs.drexel.edu \
    --cc=linux-btrfs@vger.kernel.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