From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Attach/Auth
Date: Wed, 28 Aug 2002 10:24:34 +0100 [thread overview]
Message-ID: <c73d9c29db1ac19a64ab896f4f4372a5@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
but fids can't be `dangling'. they're allocated by one request or another (eg, Tattach, Tauth, Twalk),
and deallocated by Tclunk or Tremove. they can't `dangle'.
if the client has allocated a fid, it is valid until it explicitly deallocates it.
if the client hasn't allocated a fid but uses it in a request,
it's a protocol error by the client (eg, `fid in use', or `unknown fid').
[-- Attachment #2: Type: message/rfc822, Size: 2020 bytes --]
From: "Roman V. Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Attach/Auth
Date: Wed, 28 Aug 2002 10:15:31 +0400
Message-ID: <20020828101531.A3072@unicorn.math.spbu.ru>
On Tue, Aug 27, 2002 at 08:25:49AM -0400, Russ Cox wrote:
>
> Anyhow, I just fixed the various bugs you pointed out in the manual pages.
> Let me know about any incompletenesses.
Russ, can you also add something to the effect of "fids can be dangling"
to the 9P manpages ? May be I'm being too picky, but I have a good reason --
I've learned that in a pretty hard way.
Thanks,
Roman.
next reply other threads:[~2002-08-28 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 9:24 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-30 3:10 Russ Cox
2002-08-30 3:38 ` Roman V. Shaposhnick
2002-08-30 3:41 ` Alexander Viro
2002-08-28 10:45 Russ Cox
2002-08-30 2:58 ` Roman V. Shaposhnick
2002-08-27 12:25 Russ Cox
2002-08-28 6:15 ` Roman V. Shaposhnick
2002-08-27 11:25 Russ Cox
2002-08-27 11:54 ` Lucio De Re
2002-08-26 23:24 Russ Cox
2002-08-27 5:06 ` Lucio De Re
2002-08-27 6:35 ` Lucio De Re
2002-08-26 14:02 Lucio De Re
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=c73d9c29db1ac19a64ab896f4f4372a5@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).