9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] unique identity to virtual files
Date: Tue, 15 Jan 2008 08:20:46 -0500	[thread overview]
Message-ID: <7dd2f607142effdb59218866f0fca6ec@quanstro.net> (raw)
In-Reply-To: <eff0484811b6fbdca820c1b64e274510@quintile.net>

> The subject probably doesn't explain at all well.
> 
> I have a program (A) I have written, it can optionally run atop of a
> a synthetic filesystem (B) which expands some files into directories
> of files.
> 
> The A needs to be able to tell the difference between a
> 'real' directory and one generated by B.
> 
> I could use the muid and uid and gid as magic strings, alternatively I
> could use the dev or/and type fields from stat.
> 
> Anyone have any strong feelings on the ``right'' way to do this?
> 

i don't know about "strong" feelings.  but i would think that you
would want A to not have to know about which files have been
expanded.  this defeats the purpose of B, which is to hide the
details of what it does behind a fs interface.

perhaps this means that you require A to run on B.  or perhaps
you fold B into A so that it knows the details of which file is which.

if you stick to the current design, the file name might be the easiest
to modify, perhaps followed by the Qid.

- erik


  reply	other threads:[~2008-01-15 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 13:09 Steve Simon
2008-01-15 13:20 ` erik quanstrom [this message]
2008-01-15 14:35 ` Russ Cox
2008-01-15 15:55   ` roger peppe
2008-01-15 16:29 ` Gary Wright
2008-01-15 17:21   ` Charles Forsyth

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=7dd2f607142effdb59218866f0fca6ec@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).