On Thu, Aug 16, 2012 at 08:59:01AM -0700, Bakul Shah wrote:
> On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom <[email protected]>
> wrote:
> > > What is more bizarre, with my scheme, is how to implement the meaning
> > > of ".."? If classical clients have to be able to be used, the server
> > > must create a fake name (as the penultimate component of the
> > > dirpath), that triggers the correct answer from the server.
> >
> > see defmnt.c:/^fixdotdotname for where this is handled by the kernel,
> > not the file server.
>
> It pretty much has to. Consider what happens when you do
> something like
>
> % x=`{pwd}
> % bind /sys/src tmp
> % cd tmp
> % cd ..
>
> This gets you back to $x. If you leave ".." upto the
> fileserver, you'd get back to /sys not $x. The server can't
> know the right context.
And this is why the pathname has to encode, one way or the other, the
hierarchy, to let the fileserver be context ignorant, and the user
go wherever he wants.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
