From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sun, 27 Nov 2005 22:03:17 -0500 From: Russ Cox To: erik quanstrom , Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] fsdirread v dirread() In-Reply-To: <20051128020811.6CC4EDA182@dexter-peak.quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051128020811.6CC4EDA182@dexter-peak.quanstro.net> Cc: Topicbox-Message-UUID: b2d48862-ead0-11e9-9d60-3106f5b1d025 > 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=3DN,u= ser,name=3Dquanstro,proto=3Dunix,noauto 0 0 > > which works great (after a few tweaks) except faces -i chokes and dies be= cause > 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