From: Brent Callaghan (brent@eng.sun.com)
Date: 01/13/04-12:03:54 PM Z
Message-ID: <4004330A.9080005@eng.sun.com> From: Brent Callaghan <brent@eng.sun.com> Subject: Re: [nfsv4] Global namespace for v4.1? Date: Tue, 13 Jan 2004 10:03:54 -0800 Nicolas Williams wrote: > : > Since, IMO, we must accept the primacy of the client-local namespace I'd > rather not discuss this too much and focus, instead, on how to construct > [on the wire] the domain-wide namespaces and namespace location and let > the clients be responsible for gluing the NFS v4 namespace onto their > corresponding client-local access points. Yes, customers already use global namespaces of their own making, and are very protective of them. In my experience, they react strongly to external opinions as to the structure of a global namespace. For instance, the notion of a single, well-known root, e.g. "/gfs" does not appeal to those who are already using paths like "/afs", "/net" or "/usr/local" in a global way. Neither can you paper over an imposed structure with symbolic links. As much as we might think symlinks are transparent - they are not, e.g. fire up some application GUI file chooser and instead of a friendly "/home/brent" path you see instead "/gfs/northcentral.eng/dctwg-all/mumblyfrotz/brent". Not good. Let's not get bogged down in deciding the naming structure that *we* want. Let's give customers something flexible enough that let's them build what *they* want. Brent _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4
This archive was generated by hypermail 2.1.2 : 03/04/05-02:13:09 AM Z CST