On Thu Aug 16 11:44:01 EDT 2012, [email protected] wrote:
> On Thu, Aug 16, 2012 at 09:40:22AM -0400, 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.
>
> Well, I find cleanname (libc/port/cleanname.c) doing the .. dance with
> compression. But nothing in the kernel proper..
cleanname is called by the function i indicated in devmnt.
>
> Except by allowing a new syntax .../{a,b,c,d}/foo meaning that foo has
> a, b, c and d as parents, the only way I see things working with the
> utilities and the ".." treatment is to insert a special name ensuring
> that a ".." suppression leading to this name will trigger the correct
> answer from the fileserver.
this is already the case due to union directories (as bakul points out),
and the solution has been widely discussed.
- erik
