hopefully this is not to hurried. the ... was /N/info where N is the message #. i may have been wrong on the fsreaddir.
i have o.fs -m /home/quanstro/9/upasfs -b -d -s -f /imap/mail.speakeasy.org/quanstro running. i'm reading 9p output from that. the problem is that the 9p paths that faces sends upasfs when given -i -m /home/quanstro/9/upasfs/mbox as the mailbox start with "/home/quanstro/9/upasfs". upasfs returns an error that the file doesn't exist and at that point in the code, faces exits. the magic incantation "faces -i -m mbox" works. upasfs doesn't get paths that start with "/home/quanstro/9/upasfs". i hadn't gotten to nedmail yet. erik Russ Cox <[EMAIL PROTECTED]> writes | | > 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.
