From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Thu, 16 Aug 2012 09:40:22 EDT." References: <20120803171847.GA2720@polynum.com> <501D12A1.1060906@yahoo.fr> <20120804152016.GB433@polynum.com> <20120805173639.GA395@polynum.com> <20120815173327.GA424@polynum.com> <20120815200949.4628BB85B@mail.bitblocks.com> <20120815212734.GA1190@polynum.com> <20120816034747.7FE5EB85B@mail.bitblocks.com> <20120816053428.GA427@polynum.com> Date: Thu, 16 Aug 2012 08:59:01 -0700 From: Bakul Shah Message-Id: <20120816155901.6FB72B827@mail.bitblocks.com> Subject: Re: [9fans] Multi-dimensional filesystem Topicbox-Message-UUID: aa23e044-ead7-11e9-9d60-3106f5b1d025 On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom 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.