[PATCH 0/5] Dynamic Pseudo Root

[Trond Myklebust]

On Mon, 2008-02-18 at 20:41 +0100, Gabriel Barazer wrote:

> AFAIK, you can define only one pseudoroot fs for all the NFSv4 clients, 
> so you have only one namespace to "export", right?

No! That would be a regression w.r.t. NFSv2/v3.

> What we do with a 
> real filesystem is creating directories and mount/binding them into a 
> single directory defined as a pseudoroot fs. Having different 
> permissions or visibility rules for the clients doesn't matter: you have 
> to create all the mount/bind directories. For example:
> /foo       client1
> /bar	   client2
> 
> You have to create "foo" and "bar" mounts into your pseudo root fs. The 
> better part with a pseudo fs instead of a real one is that you don't 
> have to manage all the directories and mount points by yourself since is 
> it autogenerated, and you don't have to check the consistency 
> (missing/removed mountpoints) of this pseudo root at startup (you have 
> to with a real fs).

You are entirely missing the point of the pseudofs. Its main raison d'
être is to act as a bridge between the legacy NFSv2/v3 namespace and the
NFSv4 namespace. If a proposal can't tackle converting existing NFSv2/v3
topologies, then it should go straight into the dustbin.

Trond