Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!caen!uflorida!travis!shirono From: shirono@ssd.csd.harris.com (Roberto Shironoshita) Newsgroups: comp.protocols.nfs Subject: Re: Why not export /fs /fs/subdir? Message-ID: Date: 17 Jun 91 15:26:49 GMT References: <10199@star.cs.vu.nl> Sender: news@travis.csd.harris.com Reply-To: shirono@ssd.csd.harris.com Organization: Harris Computer Systems Lines: 20 In-reply-to: sater@cs.vu.nl's message of 14 Jun 91 07:48:07 GMT In article <10199@star.cs.vu.nl> sater@cs.vu.nl (Hans van Staveren) writes: > In article felps@convex.com (Robert Felps) writes: > This means that when you export /fs/foo where /fs is a filesystem a > client can mount /fs/foo and using the NFS handle returned do the NFS > equivalent of a cd .. and start running around the rest of /fs. The big assumption in the NFS server is that the client will translate funny paths (e.g. UNIX's . and .., VMS's [-], etc.). That way, the server need not impose semantics that are beyond the concept of NFS (granted, work is still needed in this area). So, the onus is on the client to disallow the scenario you mention (the Sun NFS client translates .. all by itself). -- Roberto Shironoshita || Internet: shirono@ssd.csd.harris.com Harris Corporation || Computer Systems Division || UUCP: ...!uunet!hcx1!shirono || DISCLAIMER: The opinions expressed here are my own; they in no way reflect the opinion or policies of Harris Corporation.