From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [V9fs-developer] playing with Tim's python 9p implementation
Date: Tue, 4 Oct 2005 18:33:29 -1000 [thread overview]
Message-ID: <Pine.BSI.4.61.0510041829510.9610@malasada.lava.net> (raw)
In-Reply-To: <43429835.2000902@lanl.gov>
> I've been through this exact thing, and it has to do with auth. I'll try to
> find my modified python server to see what I did to hack around it. Also,
> newsham did put in a fix for it -- you have to invoke the server a little
> differently -- more or less turn off any auth
My fixes earlier where on the client side. The current bug is about
the server side (srv.py) not playing nicely when it gets an unexpected
version (and then later again when its doing auth, I believe).
Fix #1 - change _srvTversion to not error out if the version
does not match. It should instead return its own version.
Fix #2 - Not sure, but the code in the write() method of AuthFs
likely needs to be less restrictive.
If someone tweaks this and tests it please let me know the fix.
(I dont have v9fs installed anywhere).
> ron
Tim Newsham
http://www.lava.net/~newsham/
next prev parent reply other threads:[~2005-10-05 4:33 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
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 [this message]
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=Pine.BSI.4.61.0510041829510.9610@malasada.lava.net \
--to=newsham@lava.net \
--cc=9fans@cse.psu.edu \
/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).