On Mon, Jul 13, 2009 at 4:22 PM, Eric Van Hensbergen<eri...@gmail.com> wrote:
> Not sure how easy or difficult this would be inside the kernel -- the > central problem last time I looked at it was it was difficult to > unshare namespace after the fork. Well, my mount command cheated. When you ran the mount command, it did a fork and set CLONE_NS. You were, at that point, in a private name space. Yes, ugly, but it certainly ensured a private mount. > Of course you could check to make > sure you were not in the global namespace and error -- that should be > easy enough. That's a nice idea. You require users of the command to have a clean name space, or at least a non-global one, before you mount. That seems like a nice solution to the problem. ron
