From: "A. James Lewis" <james@fsck.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Configuring default mount options..
Date: Mon, 26 Jul 2010 12:27:35 +0100 [thread overview]
Message-ID: <1280143655.3327.22.camel@hardline> (raw)
In-Reply-To: <AANLkTimOC0qyDdv3KgY4p_vcW1YQ+f=ToaS4=81VQh4B@mail.gmail.com>
>=20
> From: Oystein Viggen <oysteivi <at> tihlde.org>
> Subject: Re: Configuring default mount options..
> Newsgroups: gmane.comp.file-systems.btrfs
> Date: 2010-07-26 06:08:54 GMT (5 hours and 4 minutes ago)
>=20
> * ["A. James Lewis"]=20
>=20
> > 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.
>=20
> There has been talk of supporting per-file (and I assume recursive
> per-directory default) attributes for raid level. Things like
> encryption and compression could fit well into such a scheme.
>=20
That's a nice solution, particularly for encryption... especially once =
the GUI file managers are able to indicate the settings.... It would se=
em to be necessary to allow these parameters to be set in the root, but=
otherwise nice.
I'm not sure if it negates the value of having default "preferences" st=
ored somwhere... certainly it would take longer to implement, but maybe=
the default parameters for all these settings are simply equivalent to=
whatever is defined in the root of each filesystem... so really one so=
lution can be a subset of the other.
>=20
> I don't believe the code for this is written yet, however.
>=20
> =C3=98ystein
> --=20
> ssh -c rot13 otherhost
>=20
>=20
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
next prev parent reply other threads:[~2010-07-26 11:27 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
2010-07-26 1:42 ` Sebastian 'gonX' Jensen
2010-07-26 11:27 ` A. James Lewis [this message]
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=1280143655.3327.22.camel@hardline \
--to=james@fsck.co.uk \
--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).