From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Listing a directory
Date: Mon, 7 Mar 2011 20:09:33 -0500 [thread overview]
Message-ID: <AANLkTi=dmNgkGfqnCbAg9J-UEhpYP_m1Sv-zO_j8HGz4@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Hi,
In 9P, if I wish to list a directory, I need to TWalk to the directory,
TOpen the directory fid from the walk, and then TRead till I have all of the
contents of the directory.
If the directory's contents do not fit in a single read, I imagine I need to
loop around TOpen / Tread / .... / Tread / TOpen, till I get the whole
contents and see the same QIDs in each open, to get a coherent listing. (is
this accurate?)
Unfortunately, a TOpened FID to a directory cannot be used for walking it
(why?); so the only use of a TOpened fid to a directory is to list it or to
get a QID. Would it be reasonable for a TOpened fid to a directory to create
a copy of the directory listing at the time of the RPC?
-- vs
[-- Attachment #2: Type: text/html, Size: 763 bytes --]
next reply other threads:[~2011-03-08 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 1:09 Venkatesh Srinivas [this message]
2011-03-08 1:17 ` Eric Van Hensbergen
2011-03-09 23:38 ` Latchesar Ionkov
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='AANLkTi=dmNgkGfqnCbAg9J-UEhpYP_m1Sv-zO_j8HGz4@mail.gmail.com' \
--to=me@acm.jhu.edu \
--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).