From: Ram Pai <linuxram@us.ibm.com>
To: Attila Kinali <attila@kinali.ch>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: bind mounts and options
Date: Fri, 28 Oct 2005 11:18:34 -0700 [thread overview]
Message-ID: <1130523514.4902.22.camel@localhost> (raw)
In-Reply-To: <20051028151343.365eecea.attila@kinali.ch>
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.
RP
>
> Attila Kinali
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" 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:[~2005-10-28 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 13:13 bind mounts and options Attila Kinali
2005-10-28 18:18 ` Ram Pai [this message]
2005-10-28 18:28 ` Shaya Potter
2005-10-29 10:22 ` Attila Kinali
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=1130523514.4902.22.camel@localhost \
--to=linuxram@us.ibm.com \
--cc=attila@kinali.ch \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.