From: Russ Cox <rsc@swtch.com>
To: quanstro@speakeasy.net,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 9pserve question
Date: Sat, 3 Dec 2005 09:26:28 -0500 [thread overview]
Message-ID: <ee9e417a0512030626g4f732bc6o864dddf040b8c9b3@mail.gmail.com> (raw)
In-Reply-To: <20051203031313.DF49018AE1F@dexter-peak.quanstro.net>
> why does 9pserve.c:451
>
> case Topenfd:
> if(m->tx.mode&~(OTRUNC|3)){
> err(m, "bad openfd mode");
> continue;
> }
>
> dissallow OTRUNC?
Because it doesn't make sense. Trust me on this.
That's case Topenfd not case Topen. See the
description of openfd in the 9pclient(3) man page.
Topenfd is a special message only recognized by
9pserve and only emitted by the 9pclient library.
It's not used by anything else.
> this means that
>
> ; mount $home/9/upasfs
> ; echo delete mbox 24 > $home/9/upasfs/ctl
>
> and
>
> ; mount $home/9/factotum
> ; echo delkey > $home/9/factotum/ctl
>
> don't work. you need to replace '>' with '>>'.
I can't imagine why mounting (presumably this is Linux)
would cause the kernel to issue Topenfds. Your
problem is probably elsewhere. Perhaps the v9fs
module is sending a Tcreate and then when that fails
not trying a Topen OTRUNC as a fallback.
If you set verbose9pserve=1 in your environment
before starting one of these programs, then you can
see the messages going in and out.
Russ
next prev parent reply other threads:[~2005-12-03 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 3:13 erik quanstrom
2005-12-03 14:26 ` Russ Cox [this message]
2005-12-03 14:35 ` erik quanstrom
2005-12-03 14:54 ` erik quanstrom
2005-12-03 15:53 ` erik quanstrom
[not found] ` <6114CFD8-C785-425A-AEDB-5397D83E069C@cibernet.com>
2005-12-03 17:00 ` erik quanstrom
2005-12-03 17:03 ` erik quanstrom
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=ee9e417a0512030626g4f732bc6o864dddf040b8c9b3@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=quanstro@speakeasy.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).