Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [PATCH] private mounts | From | Ram <> | Date | Sat, 30 Apr 2005 09:47:06 -0700 |
| |
On Sat, 2005-04-30 at 01:33, Christoph Hellwig wrote: > On Mon, Apr 25, 2005 at 08:07:34PM +0100, Jamie Lokier wrote: > > Pavel Machek wrote: > > > > > ... is the same as for the same question with "set of mounts" replaced > > > > > with "environment variables". > > > > > > > > Not quite. > > > > > > > > After changing environment variables in .profile, you can copy them to > > > > other shells using ". ~/.profile". > > > > > > > > There is no analogous mechanism to copy namespaces. > > > > > > Actually, after you add right mount xyzzy /foo lines into .profile, > > > you can just . ~/.profile ;-). > > > > Is there a mount command that can do that? We're talking about > > private mounts - invisible to other namespaces, which includes the > > other shells. > > > > If there was a /proc/NNN/namespace, that would do the trick :) > > I don't think you need a /proc/NNN/namespace, /proc/NNN/mounts already > contains a mount table. It's pretty trivial to write a small shellscript > to parse that, compare with the current namespace and do all mount/umounts > to make them fit the other processes namespace. Real problem here are > filesystems that don't implement ->show_options or do so only partially > so that some options are lost.
The other problem is: How would new mounts in any of these namespaces propogate to other namespaces owned by the same user?
I mean, how will the other namespace's belonging to the same user, be able to pull the mounts into their namespaces? shared subtree won't be a solution because these namespaces won't have a parent-child relationship to begin with, for the propogation to be set up.
RP
> > - > 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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |