From: Shaya Potter Subject: Re: bind mounts and options Date: Fri, 28 Oct 2005 14:28:58 -0400 Message-ID: <1130524139.8058.114.camel@localhost.localdomain> References: <20051028151343.365eecea.attila@kinali.ch> <1130523514.4902.22.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Attila Kinali , linux-fsdevel@vger.kernel.org Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:41709 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S1030568AbVJ1S3Y (ORCPT ); Fri, 28 Oct 2005 14:29:24 -0400 To: Ram Pai In-Reply-To: <1130523514.4902.22.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 2005-10-28 at 11:18 -0700, Ram Pai wrote: > On Fri, 2005-10-28 at 06:13, Attila Kinali wrote: > > Moin, > > > > I wanted to ask whether there is a technical reason > > why bind mounts do not honour options passed to it. > > > > It would be a really cool feature to be able > > to mount certain parts of the file system into > > a chroot enviroment read only, so that it couldnt > > be modified, but still be changed by a user outside > > the chroot. > > > > At least i've seen a few patches floating around > > that add at least the ro option, so i guess it should > > not be too hard. > A bind mount to a different location creates a new mount-instance of the > underlying filesytem. > If the underlying filesystem can handle multiple instances of itself > being mounted with different read-options, this should be possible. > But I dont think currently that is the case. one could create a really simple stackable file system that did this, use fist, generate base0fs, and edit the code to disallow all function paths that can change the filesystem. It's not a complete situation, as meta data (access time...) would still be updated.