Alexander Viro <email@example.com> writes:
> There is no such thing as "global namespace", the only reason why
> it looks that way now is the lack of CLONE_NAMESPACE. Per-user namespaces
> are bogus, what you want is the ability to copy namespace upon clone()
> instead of sharing the thing with parent.
Unfortunately, there are frequently administrative reasons to say,
`everyone unmount this right now, we need to take this disk offline'
(chance to everyone's namespace)
`mount this so that all my daemons can see it' (change to namespace
unrelated to yours)
`everyone mount this right now, that disk is replaced and /opt/glurk is
back where it should be'.
I don't think automounters suffice for all of this --- and automounters
are arguably overkill for this sort of thing, anyway. Is there a way to
say that, if some processes' namespaces are clone/separated from all the
-- `It's as if Hal Clement expanded fragments of a novel by H.P. Lovecraft.' --- Jake Kesinger on the novel _Darwinia_.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:27 EST