Re: [9fans] fsdirread v dirread()

[Russ Cox <rsc@swtch.com>]

> i've been running linux 2.6.14 and mounting upasfs via
> this mtab entry:
>
> /tmp/ns.quanstro.:0/upasfs      /home/quanstro/9/upasfs 9P      uid=N,user,name=quanstro,proto=unix,noauto      0 0
>
> which works great (after a few tweaks) except faces -i chokes and dies because
> fsreaddir() ends up sending upasfs the path "/home/quanstro/upasfs/mbox/..."
> instead of "mbox/...". i'm guessing that the named sockets in $NAMESPACE
> need this extra information.

some more information would be helpful.
fsreaddir reads a directory.  it doesn't send paths.
what is the ... that you're eliding?

i am guessing that you are looking at loadmboxfaces.
the results of dirread are used in that loop, but
dirread is most definitely not the problem.

when you click on a face, faces sends a plumbing
message containing the message directory.
that message should contain the entire directory,
or else the program the plumber invokes will not
know how to handle it.

plumber in turn will run
    window -r 4 120 750 600 upas/nedmail -s $0
and given that there is no window script (yet),
that's going to fail.

you can see the plumbing messages by running
    9p read plumb/showmail
or maybe
    cat /home/quanstro/9/plumb/showmail
in another window.  check that the path is the full one.

then: does
    upas/nedmail -s /home/quanstro/9/upasfs/mbox/1/
work?  it should.  if not, figure out what nedmail is
doing wrong.

russ