From: Anthony Martin <ality@pbrane.org>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: 9p(2) and walk1
Date: Mon, 15 Feb 2021 13:35:43 -0800 [thread overview]
Message-ID: <YCrpL0EKXTu/q5GP@alice> (raw)
In-Reply-To: <25c14ae7d3170c12da15b2a1f47fd646@nohup.io>
pouya+lists.9fans@nohup.io once said:
> Are these subtle differences (the two in the man page and the third in
> code) intentional? It's my first time implementing a 9P file system
> so apologies if I'm missing something basic.
It's actually just a case of forgetting to update the man page.
In early February 2003, Russ was cleaning up lib9p and changed
the code to check that fid->qid and qid were exactly the same.
He updated the man page accordingly. However, Dan Cross noticed
that it broke some existing code. Russ then relaxed the client
requirements and had lib9p just assign qid to fid->qid. The man
page wasn't updated to reflect the change.
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Okay, who's been playing with the cheese wiz?
From: "Russ Cox" <rsc@plan9.bell-labs.com>
Date: Sun, 9 Feb 2003 16:51:01 -0500
Message-ID: <fb9812bf58e9e8395b3b3635a229e708@plan9.bell-labs.com>
[...]
I changed lib9p to do a few more checks that the
client code is behaving, and your execnet crash
shows that lib9p thinks execnet is not behaving.
It turns out that actually lib9p is not behaving -- I was
trying to clean up this particular detail (whether a
walk function should set both fid->qid and *qid),
because it always confuses me, and I got confused.
I just put out a new srv.c that makes reasonable
demands of the clients.
[...]
Cheers,
Anthony
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tb39d71a5497bba2d-M26c5e627eb106c505ce67b9b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2021-02-15 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:59 [9fans] " pouya+lists.9fans
2021-02-15 21:35 ` Anthony Martin [this message]
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=YCrpL0EKXTu/q5GP@alice \
--to=ality@pbrane.org \
--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).