From: Russ Cox <rsc@swtch.com>
To: "Anselm R. Garbe" <garbeam@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 9P reading directory contents
Date: Thu, 29 Sep 2005 10:18:21 -0400 [thread overview]
Message-ID: <ee9e417a0509290718q17d7465epfdccd1ae8e4f63b5@mail.gmail.com> (raw)
In-Reply-To: <89d1e7b8050929040246dbda80@mail.gmail.com>
> 1) Topen with root fid and Tread with root fid
> This worked as expected
Good.
> 2) Just Tread with root fid
> This worked also the same, but I didn't expected that it is possible
> to read directory contents without preparing the fid for I/O through
> Topen.
Not good.
> Anyone can tell me if this is intended and why?
It's not intended. It works because acme assumes it is talking
to an honest client, one who would never do (2). Other servers
do more sanity checking. Try fossil or the ones based on lib9p.
Russ
prev parent reply other threads:[~2005-09-29 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 11:02 Anselm R. Garbe
2005-09-29 14:18 ` Russ Cox [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=ee9e417a0509290718q17d7465epfdccd1ae8e4f63b5@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
--cc=garbeam@gmail.com \
/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).