9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p question
Date: Thu, 30 Jul 2009 13:30:45 -0300	[thread overview]
Message-ID: <d1c554290907300930o523c248h7336550e3329cae5@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0907300908k3bd5edd2mb4094c4e88d12170@mail.gmail.com>

On Thu, Jul 30, 2009 at 1:08 PM, Russ Cox<rsc@swtch.com> wrote:
> 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.
>

it would surely make it easier for unix implementations. i have had
plenty of issues with that in o9fs.

but as yourself pointed out, what would that walk mean?

iru



  reply	other threads:[~2009-07-30 16:30 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
2009-07-30 16:30   ` Iruata Souza [this message]
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=d1c554290907300930o523c248h7336550e3329cae5@mail.gmail.com \
    --to=iru.muzgo@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).