On 10/4/05, erik quanstrom <[EMAIL PROTECTED]> wrote:
> that number is (unsigned long)-1L on a 32bit machine.
>
> i'd bet (sight unseen) that the python code is using unsigned longs for the 
> fids
> and everybody else is using a long with -1 as an error code.
>

I figured it was -1 :).  I just didn't think that it was an error code.

Still interesting.  When I have an error trying to mount the python 9p
server from inferno I don't get that error... only with v9fs.

Dave

> erik
>
> David Leimbach <[EMAIL PROTECTED]> writes
>
> |
> | I can mount it from Plan 9 but when I try to mount it with v9fs I get
> | errors on the server side:
> |
> | On Mac OS X I do:
> | "sudo  python srv.py -r /Users/dave/Desktop dave homework.net"
> |
> |
> |
> | On plan 9 it's just
> | "9fs fuji"
> |
> | and things work well.
> |
> | On Linux I do:
> | "mount -oname=dave,noextend -t 9P 192.168.1.100 /mnt/9"
> |
> | and I get:
> | "mount: permission denied" in linux
> |
> | and the 9p in python gives the following:
> |
> | "serving: '192.168.1.81',35556
> | Error fid 4294967295 not in use
> | client EOF"
> |
> | Not clear what's happening there.
> |
> | Before I used noextend I got errors on the server side about not
> | understanding 9p2000.u.  Totally expected :).
> |
> | I'm currently using the Python 9p as a quick replacement for testing
> | something like u9fs now that I can't really build it on anything but
> | linux.
> |
> | I'm not terribly interested in hacking on u9fs right now either.  I've
> | got bigger fish to fry and this Python 9p server may do exactly what I
> | want for a particular project I have in mind.
> |
> | Dave
>

Reply via email to