From: Eric Van Hensbergen <ericvh@gmail.com>
To: David Leimbach <leimy2k@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: erik quanstrom <quanstro@quanstro.net>
Subject: Re: [9fans] Re: [V9fs-developer] playing with Tim's python 9p implementation
Date: Tue, 4 Oct 2005 09:43:47 -0500 [thread overview]
Message-ID: <a4e6962a0510040743y5d91a109ua76939439991d92a@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60510040741o75eab9f2q9e9c4854f1f93aaf@mail.gmail.com>
If you turn on the debug=1 during mount you should get the error in
your syslog. Or if you really want a flood of debug go for debug=255.
Either way it'll let us know what's going on. It probably has to do
with auth, it may also have to do with what tid is sent during
version/attach, there is some variation between the various systems on
what is expected.
-eric
On 10/4/05, David Leimbach <leimy2k@gmail.com> wrote:
> On 10/4/05, erik quanstrom <quanstro@quanstro.net> 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 <leimy2k@gmail.com> 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
> >
>
next prev parent reply other threads:[~2005-10-04 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3e1162e60510031714y15fa11b0tf15a3bc314fe26e0@mail.gmail.com>
[not found] ` <20051004120350.44AA61418FF@dexter-peak.quanstro.net>
2005-10-04 14:41 ` David Leimbach
2005-10-04 14:43 ` Eric Van Hensbergen [this message]
2005-10-04 14:56 ` Ronald G Minnich
2005-10-04 15:01 ` David Leimbach
2005-10-05 23:26 ` C H Forsyth
[not found] ` <17359dff2944f0b6ab9858ace89d5cac@vitanuova.com>
2005-10-05 23:40 ` David Leimbach
2005-10-04 15:18 ` Eric Van Hensbergen
2005-10-04 15:22 ` David Leimbach
2005-10-05 4:33 ` Tim Newsham
2005-10-05 4:33 ` Tim Newsham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4e6962a0510040743y5d91a109ua76939439991d92a@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=leimy2k@gmail.com \
--cc=quanstro@quanstro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).