Re: does using different uid/gid/forceuid/... mount options for different subvolumes work / does fuse.bindfs play nice with btrfs?

> I intend to provide different "views" of the data stored on > btrfs subvolumes. e.g. mount a subvolume in location A rw; > and ro in location B while also overwriting uids, gids, and > permissions. [ ... ] That's not how UNIX/Linux permissions and ACLs are supposed to work, perhaps you should

Re: does using different uid/gid/forceuid/... mount options for different subvolumes work / does fuse.bindfs play nice with btrfs?

Ok, thanks for the clarification. Bindfs will continue to live on my machines then! Regards, Alexander On 20 June 2017 at 17:15, Hugo Mills wrote: > On Tue, Jun 20, 2017 at 04:35:48PM +0200, Alexander Peganz wrote: >> Hello everyone, >> >> I intend to provide different

Re: does using different uid/gid/forceuid/... mount options for different subvolumes work / does fuse.bindfs play nice with btrfs?

On Tue, Jun 20, 2017 at 04:35:48PM +0200, Alexander Peganz wrote: > Hello everyone, > > I intend to provide different "views" of the data stored on btrfs subvolumes. > e.g. mount a subvolume in location A rw; and ro in location B while > also overwriting uids, gids, and permissions. > In the past

does using different uid/gid/forceuid/... mount options for different subvolumes work / does fuse.bindfs play nice with btrfs?

Hello everyone, I intend to provide different "views" of the data stored on btrfs subvolumes. e.g. mount a subvolume in location A rw; and ro in location B while also overwriting uids, gids, and permissions. In the past I have been using fuse.bindfs for this. Now I'm trying to find out if there