From: "roger peppe" <rogpeppe@gmail.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 15:55:13 +0000 [thread overview]
Message-ID: <df49a7370801150755n739fd7ceoce771bce677349fa@mail.gmail.com> (raw)
In-Reply-To: <20080115143538.0E9A81E8C1C@holo.morphisms.net>
On Jan 15, 2008 2:35 PM, Russ Cox <rsc@swtch.com> wrote:
> the usual answer is "don't do that."
which i agree with, but assuming you *are* doing that:
> using the uid/gid would make the most sense to me,
> in that it would be the least unexpected.
or maybe even muid, as very little uses it, and
in some sense perhaps the synthetic filesystem
is the last thing that modified the (appearance of) the
original file. the original muid isn't necessarily lost,
as files within the synthetic directory could hold
the original.
next prev parent reply other threads:[~2008-01-15 15:55 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 [this message]
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=df49a7370801150755n739fd7ceoce771bce677349fa@mail.gmail.com \
--to=rogpeppe@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).