Messages in this thread | | | Subject | Re: per-process namespace? | From | Ram Pai <> | Date | 30 Jun 2004 18:32:41 -0700 |
| |
On Wed, 2004-06-30 at 17:14, Serge E. Hallyn wrote: > > The per-process namespace concept comes in handy here except for the > > static nature of the namespace. In the sense, any changes to the system > > namespace do not reflect in the children namespace. > > Static? > > It's not static! It's private, as advertised.
> It sounds like you're asking (or your customer is asking) for > copy-on-write namespaces :) > Yes! exactly right. A copy-on-write namespace. That way we dont even have to invent new interfaces to define maskable mount-points that I mentioned earlier.
- 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/
| |