From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] implmenting /mnt/9/clone
Date: Fri, 29 Jul 2005 13:19:13 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0507291315160.15596@enigma.lanl.gov> (raw)
I'm playing around with the p9p ramfs server, and was wondering about the
best way to implement a file for clone.
e.g. I have /mnt/9/clone, and when clone is opened, I want to to mean that
/mnt/9/1/ctl is created and fid for that file returned to client, and the
next open of clone gets /mnt/9/2/ctl, etc. As usual, a read of the ctl
would return the # for that ctl file.
I can think of a couple of ways to
do it, with the simplest involving:
- when clone is opened, create #/ctl, e.g. 3/ctl
- swap the qids for clone and the #/ctl file
Any comments on this, or hidden gotchas, or ...
I'm pretty sure this would work for Linux 9p clients, but am not sure
about the overal cleanliness of this approach, or if there is some better
way to do it.
ron
next reply other threads:[~2005-07-29 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:19 Ronald G. Minnich [this message]
2005-07-29 19:24 ` Eric Van Hensbergen
2005-07-29 19:47 ` Ronald G. Minnich
2005-07-29 20:54 ` Eric Van Hensbergen
2005-07-29 20:58 ` Russ Cox
2005-07-29 19:39 ` Russ Cox
2005-07-29 23:13 ` Ronald G. Minnich
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=Pine.LNX.4.58.0507291315160.15596@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--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).