From: Gary Wright <gwtmp01@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] unique identity to virtual files
Date: Tue, 15 Jan 2008 11:29:32 -0500 [thread overview]
Message-ID: <398A1F6D-E0E9-4D52-B8F2-D0661D8A0516@mac.com> (raw)
In-Reply-To: <eff0484811b6fbdca820c1b64e274510@quintile.net>
On Jan 15, 2008, at 8:09 AM, Steve Simon wrote:
> 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.
Any reason why B, since it is already synthetic, can't synthesize
a special file with a well-known name that can be used to signal
the virtual expansion? It seems simpler than overloading the
semantics of a stat entry. You could even use the 'aname' of the
attach message to specify the name of the sigil file if you need
it to be dynamic.
Gary Wright
next prev parent reply other threads:[~2008-01-15 16:29 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
2008-01-15 14:35 ` Russ Cox
2008-01-15 15:55 ` roger peppe
2008-01-15 16:29 ` Gary Wright [this message]
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=398A1F6D-E0E9-4D52-B8F2-D0661D8A0516@mac.com \
--to=gwtmp01@mac.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).