From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p question
Date: Thu, 30 Jul 2009 09:08:14 -0700 [thread overview]
Message-ID: <dd6fe68a0907300908k3bd5edd2mb4094c4e88d12170@mail.gmail.com> (raw)
In-Reply-To: <f75780240907300828s1ddeeb13laee217ebeb2a31e6@mail.gmail.com>
On Thu, Jul 30, 2009 at 8:28 AM, Venkatesh Srinivas<me@acm.jhu.edu> wrote:
> How come you can't TWalk along an open Fid?
In the original 9P protocol, that didn't make sense,
because walk always updated the fid it was starting from.
If you open a fid and then walk it elsewhere,
is it still open? Is that an implicit close?
And the operation isn't needed by the Plan 9 kernel anyway,
so out it goes.
In the current 9P protocol, I think it would be fine to
allow a walk to start at an open fid as long as newfid
was being used to create a new fid. This would
make it easy to implement fchdir on Unix.
Russ
next prev parent reply other threads:[~2009-07-30 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 15:28 Venkatesh Srinivas
2009-07-30 16:08 ` Russ Cox [this message]
2009-07-30 16:30 ` Iruata Souza
2009-07-30 20:44 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2000-02-18 10:47 Roman
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=dd6fe68a0907300908k3bd5edd2mb4094c4e88d12170@mail.gmail.com \
--to=rsc@swtch.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).