From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Thu, 11 Nov 2010 19:35:42 -0800 [thread overview]
Message-ID: <AANLkTikvbZ0puqG=T01ZB6hSGKPmmzBFByU43oFn43A3@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=RGkzqgWmwSjxsa3ok4dB+9LTFWJp+DOzz7o=E@mail.gmail.com>
You can keep srv() from eating Tattach's and Tauth's without numeric
userids with the following:
--- a/src/cmd/9pserve.c Wed Nov 03 15:49:22 2010 -0400
+++ b/src/cmd/9pserve.c Thu Nov 11 19:27:02 2010 -0800
@@ -440,6 +440,8 @@
m->tx.uname = getuser(); /* what srv.c used */
repack(&m->tx, &m->tpkt, c->dotu);
}
+ if(dotu && !c->dotu)
+ repack(&m->tx, &m->tpkt, dotu);
break;
case Twalk:
if((m->fid = gethash(c->fid, m->tx.fid)) == nil){
@@ -474,6 +476,8 @@
continue;
}
m->afid->ref++;
+ if(dotu && !c->dotu)
+ repack(&m->tx, &m->tpkt, dotu);
break;
case Tcreate:
if(dotu && !c->dotu &&
(m->tx.perm&(DMSYMLINK|DMDEVICE|DMNAMEDPIPE|DMSOCKET))){
knieriem also proposed a fix at:
http://code.swtch.com/plan9port/issue/38/9pserve-not-translating-9p2000-client-msgs
Russ does this approach blow up your ssh-agent?
Noah
On Wed, Nov 10, 2010 at 6:31 AM, Russ Cox <rsc@swtch.com> wrote:
>>> Factotum doesn't answer that message.
>>> You need to be looking at 9pserve.
>>
>> maybe i'm missing something, but 9pserve is also the
>> mechanism behind plumb, and it works. why would
>> p9serve be broken, but only for factotum? more likely
>> that drawterm itself is broken?
>
> It's always hard to say which program is broken
> when two programs can't talk to each other.
> I was only trying to point out that the two programs
> involved are drawterm and 9pserve, not drawterm
> and factotum (you had made changes to factotum
> in hopes that would fix it).
>
> I suspect the problem has to do with the so-called
> 9P2000.u protocol negotiation that 9pserve supports.
>
> Russ
>
>
next prev parent reply other threads:[~2010-11-12 3:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans [this message]
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah
2010-11-09 19:27 ` Russ Cox
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='AANLkTikvbZ0puqG=T01ZB6hSGKPmmzBFByU43oFn43A3@mail.gmail.com' \
--to=noah.evans@gmail.com \
--cc=9fans@9fans.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).