From: "Fariborz 'Skip' Tavakkolian" <fst@real.com>
To: 9fans@cse.psu.edu
Subject: [9fans] 9P2000 question
Date: Tue, 24 Jul 2001 12:43:13 -0700 [thread overview]
Message-ID: <3.0.5.32.20010724124313.013e2c60@mail.real.com> (raw)
How are additional (ad-hoc or not currently accounted for) file attributes
added to the filesystem? In re-reading the stat/wstat description for 9P2000
there does not seem to be a provision for that. What I think would be useful
is to have additional attributes which may be filesystem specific and that
only certain application may care to know about, etc.
next reply other threads:[~2001-07-24 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 19:43 Fariborz 'Skip' Tavakkolian [this message]
2001-07-24 20:17 rob pike
2001-07-24 21:34 ` Dan Cross
2001-07-24 21:50 rob pike
2001-07-24 22:34 ` Fariborz 'Skip' Tavakkolian
2001-07-24 22:43 ` William K. Josephson
2001-07-24 23:14 ` Fariborz 'Skip' Tavakkolian
2001-07-25 2:39 ` William K. Josephson
2001-07-25 15:51 ` Dan Cross
2001-07-24 22:38 ` Dan Cross
2001-07-24 23:53 rob pike
2001-07-26 3:14 David Gordon Hogan
2001-07-26 18:28 ` Dan Cross
2001-07-26 13:06 presotto
2001-07-26 17:55 ` Fariborz 'Skip' Tavakkolian
2001-07-26 18:29 ` Dan Cross
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=3.0.5.32.20010724124313.013e2c60@mail.real.com \
--to=fst@real.com \
--cc=9fans@cse.psu.edu \
/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).