From mboxrd@z Thu Jan 1 00:00:00 1970 From: "A. James Lewis" Subject: Re: Configuring default mount options.. Date: Mon, 26 Jul 2010 12:27:35 +0100 Message-ID: <1280143655.3327.22.camel@hardline> References: <1280105806.3327.4.camel@hardline> <1280107386.3327.8.camel@hardline> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 To: linux-btrfs@vger.kernel.org Return-path: In-Reply-To: List-ID: >=20 > From: Oystein Viggen 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