From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] implmenting /mnt/9/clone
Date: Fri, 29 Jul 2005 14:24:03 -0500 [thread overview]
Message-ID: <a4e6962a050729122471b773a0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507291315160.15596@enigma.lanl.gov>
On 7/29/05, Ronald G. Minnich <rminnich@lanl.gov> wrote:
>
> 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.
>
One small problem I've noticed with v9fs and clone style file systems
(in particular ACME) -- make sure things like stat don't trigger the
creation of the resource, otherwise things like ls -l will end up
creating windows, etc. I haven't found a good way around this from a
Linux perspective.
-eric
next prev parent reply other threads:[~2005-07-29 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:19 Ronald G. Minnich
2005-07-29 19:24 ` Eric Van Hensbergen [this message]
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=a4e6962a050729122471b773a0@mail.gmail.com \
--to=ericvh@gmail.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).