Re: [9fans] File server for NT

[Andrew Simmons <andrew.simmons@xtra.co.nz>]

in article 20030516050016.GA69277@mero.morphisms.net, William K. Josephson
at jkw@eecs.harvard.edu wrote on 5/16/03 5:01 PM:

> On Fri, May 16, 2003 at 03:53:16PM +1200, Andrew Simmons wrote:
>> Sorry to be obtuse, but are you saying that 9fs is attempting to run pwd or
>> ls on the remote system running u9fs?
>
> No, your shell.  When you tell the shell to execute 'foo', it
> will, for each directory, d, in the path, try to execute d/foo.
> It so happens that by default the first directory in the path
> is ..
>
>> Re the path name, I have to confess I only looked at it after I'd
>> re-formatted it, possibly erroneously, but I'm confused about the references
>> to dot. From walk(5): The name "." (dot), meaning the current directory, is
>> not used in the protocol.
>
> The protocol has nothing to do with it; you're just seeing an
> artifact of how the shell works.
>
I think we're talking at cross-purposes here. I'm running Windows 2000, and
don't knowingly have a shell as such. I'm running Plan 9 in a VMWare virtual
machine, talking to an NT service similar to u9fs on the same physical
machine. In the Plan 9 VM, I connect to the NT service by typing something
like:
9fs ajs
I then authenticate via 9pany if necessary. After that, the drives on my
machine are visible from the Plan 9 VM as /n/ajs/c and so on. If my current
directory on the Plan 9 VM is /n/ajs/c/nurdge, and I execute the command
pwd, then the first thing that seems to happen in the NT service is that I
get a 9p2000 message to walk to /n/ajs/c/nurdge/pwd. This fails, but the pwd
command eventually produces the right result. Similarly with the ls command.
What I was trying to find out is, does 9fs send the walk messages I have
attempted to describe? If so, why? If not, am I hallucinating?