9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Sat, 13 Nov 2010 09:31:43 +0100	[thread overview]
Message-ID: <20101113083143.GA1101@polynum.com> (raw)
In-Reply-To: <AANLkTi=fTWYdgCo3HTWAjkz=weWL7Y_Q=LTQVuXOZBaj@mail.gmail.com>

On Fri, Nov 12, 2010 at 02:20:35PM -0800, ron minnich wrote:
> On Fri, Nov 12, 2010 at 2:15 PM, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> 
> > No, that's true.  I think this is actually a huge open issue for
> > existing distributed file systems in general and I'm not sure of a
> > good way around.
> 
> yeah, we had lots of discussion of this about 8 years ago with 9grid
> and never worked it out. What's your global identify? How do you name
> it? How do you map it to a local identity? I have no clue.

The problem with strings is that they are human oriented and human
dependent, on mood and/or trend. Numbers are agnostic.

Isn't a solution à la IP network numbers possible? I mean, a user,
whatever string is locally associated to it (and this may change), is
uniquely identified by a number that could encode a domain (with some
numbers being absolutely local), the conversion between string to number
being local (I'm called "god" on my personal systems, and may be called
"dummy" elsewhere; well, in fact "god" is "root" on Unices, and this 
"god" is only a local thing, with external systems don't believing in it
at all), and negociation being only with numbers.

And separate logical user from physical user: a physical user can be,
depending on the task, several distinct logical users; but the reverse
is true: several distinct physical users can be an uniq logical user.

This changes the way one thinks about the sharing of randomly writable
files: only "the" (logical) user of a file can randomly write 
(by randomly, I mean not append) a file; but there can be several 
concurrent instances of "the" user writing to the file (an instance
of a user is called a terminal; and a terminal is a temporary view
of the data).

And there are group writable files that are only append writable so long
as a new record doesn't invalidate the previous ones [partition]
(hence distinct logical users sharing a group writable file don't
care about other writes when reading; when writing, an identifier
is returned, and if the record already exists, added by another user,
the existing identifier is returned, else it is added and the new
identifier is returned).

The use of numbers mapping to a string that can change is the principle
I have adopted with my CVS: the "projects" are only numbers, and if the
mood (or the "marketing") change, only the string associated changes,
the hierarchy is left alone since the numbers are fixed from start.
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  parent reply	other threads:[~2010-11-13  8:31 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 21:13 erik quanstrom
2010-11-09  3:37 ` erik quanstrom
2010-11-09 17:41   ` David Leimbach
2010-11-09 17:51     ` erik quanstrom
2010-11-10  0:37       ` erik quanstrom
2010-11-10  1:49         ` Russ Cox
2010-11-10  6:46           ` erik quanstrom
2010-11-10 14:31             ` Russ Cox
2010-11-12  3:35               ` Noah Evans
2010-11-12  5:34                 ` erik quanstrom
2010-11-12  5:46                   ` Noah Evans
2010-11-12  6:03                   ` Noah Evans
2010-11-12  6:19                     ` Russ Cox
2010-11-12  6:25                       ` Noah Evans
2010-11-12  9:07                       ` EBo
2010-11-12 15:12                         ` David Leimbach
2010-11-12 15:19                       ` Eric Van Hensbergen
2010-11-12 15:35                         ` erik quanstrom
2010-11-12 15:55                         ` Russ Cox
2010-11-12 16:22                           ` Eric Van Hensbergen
2010-11-12 19:55                             ` ron minnich
2010-11-12 20:23                               ` erik quanstrom
2010-11-12 20:31                                 ` Eric Van Hensbergen
2010-11-12 20:37                                   ` ron minnich
2010-11-12 20:30                               ` Eric Van Hensbergen
2010-11-12 20:41                                 ` ron minnich
2010-11-12 22:15                                   ` Eric Van Hensbergen
2010-11-12 22:20                                     ` ron minnich
2010-11-12 22:36                                       ` Russ Cox
2010-11-13  8:31                                       ` tlaronde [this message]
2010-11-13 23:42                                         ` Dave Eckhardt
2010-11-14 22:49                                       ` Nathaniel W Filardo
2010-11-15 16:22                                         ` erik quanstrom
2010-11-15 17:40                                           ` Nathaniel W Filardo
2010-11-15 17:50                                   ` John Floren
2010-11-12 21:12                               ` Russ Cox
2010-11-09 18:08     ` yy
2010-11-09 19:17     ` Bakul Shah
2010-11-09 19:27     ` Russ Cox

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=20101113083143.GA1101@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).