linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "A. James Lewis" <james@fsck.co.uk>
To: Sebastian 'gonX' Jensen <gonx@overclocked.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Configuring default mount options..
Date: Mon, 26 Jul 2010 02:23:06 +0100	[thread overview]
Message-ID: <1280107386.3327.8.camel@hardline> (raw)
In-Reply-To: <AANLkTikNemTBWO8ChQ-XYdP4gp=1zKt5EMyzdzLrxgWq@mail.gmail.com>

On Mon, 2010-07-26 at 03:10 +0200, Sebastian 'gonX' Jensen wrote:
> On 26 July 2010 02:56, A. James Lewis <james@fsck.co.uk> wrote:
> > If using BTRFS on a removable drive... it may be a problem for example,
> > to always mount with compression, or always mount with encryption (If
> > supported in future)... perhaps btrfstune could define default mount
> > options, such as compression... so if there is a BTRFS filesystem on a
> > removable hard drive, or flash stick, the filesystem can be configured
> > to mount with compression by default.
> >
> > Maybe there is a way to do this already, but it seems like the
> > filesystem itself should contain preferences for the way it is used
> > under those circumstances.
> >
> > A. James Lewis
> >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> That's actually a good idea. Perhaps an override flag could be
> specified in case you do not wish to use said default mount options?
> 
Indeed, if any mount options are specified they would override
defaults... but if you plug in a removable drive, you there's no way to
specify mount options, but it's quite likley that you would want some,
like compression for example.


> Regards,
> Sebastian J.



  reply	other threads:[~2010-07-26  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26  0:56 Configuring default mount options A. James Lewis
2010-07-26  1:10 ` Sebastian 'gonX' Jensen
2010-07-26  1:23   ` A. James Lewis [this message]
2010-07-26  1:42     ` Sebastian 'gonX' Jensen
2010-07-26 11:27       ` A. James Lewis
2010-07-26  6:08 ` Oystein Viggen

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=1280107386.3327.8.camel@hardline \
    --to=james@fsck.co.uk \
    --cc=gonx@overclocked.net \
    --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;
as well as URLs for NNTP newsgroup(s).