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] Multi-dimensional filesystem
Date: Fri,  3 Aug 2012 21:25:44 +0200	[thread overview]
Message-ID: <20120803192544.GA4961@polynum.com> (raw)
In-Reply-To: <CAJSxfmKN55K7URLEUw+vA_YSeSySVF+V7YAktMvzxPvCbuVptg@mail.gmail.com>

On Fri, Aug 03, 2012 at 11:58:08AM -0700, Skip Tavakkolian wrote:
> if i understand correctly, this is one way it could be done (i think):
>
> * built a graph representing the structure
> * create a file server that given a graph and a root node, synthesizes
> a hierarchy,  AND
> * on every walk to a node launches a copy of itself with the same
> graph but the new node as the root AND
> * mounts the newly launched copy of it self under that node (like exportfs).

Interesting. I guess the "children"/"parents" problem could be tricked by this
translation (changing the origin on each node, and in fact presenting
"parents" as one subdirs tree [reverse hierarchy] and the real "children"
classically the other part (the negative could be precisely parents)).
But in this case the equivalent of "cd .." on root would indeed goes in
a subdir, unless root is absolute root...

What is typical is that n 9P, walk takes whether a subdir or the
previous, that is the ".." is really a local variable meaning
"whatever was before" and not something hard encoded in the current
file.

The problem of implementing something efficient for the storage
(not serving it) is another matter.

The "lack" of links (whether hard or symbolic) on Plan9 could seem
to suppress some facilities. But since this does not give all, even not
a lot (this does not address multidimensional), it happens that it
could be easier to implement something like this in a Plan9 world...

Thanks!
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2012-08-03 19:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 17:18 tlaronde
2012-08-03 18:58 ` Skip Tavakkolian
2012-08-03 19:25   ` tlaronde [this message]
2012-08-03 21:08 ` Burton Samograd
2012-08-03 21:12   ` Kurt H Maier
2012-08-03 21:17     ` Burton Samograd
2012-08-04  6:13   ` tlaronde
2012-08-04 10:56     ` Aram Hăvărneanu
2012-08-04 15:00       ` tlaronde
2012-08-04 12:16 ` Nicolas Bercher
2012-08-04 15:20   ` tlaronde
2012-08-05 15:29     ` Charles Forsyth
2012-08-05 17:36       ` tlaronde
2012-08-15 16:04         ` Eugene Gorodinsky
2012-08-15 17:33           ` tlaronde
2012-08-15 20:09             ` Bakul Shah
2012-08-15 20:17               ` erik quanstrom
2012-08-15 21:00                 ` Bakul Shah
2012-08-16  1:38                   ` erik quanstrom
2012-08-16  4:06                     ` Bakul Shah
2012-08-16 13:45                       ` erik quanstrom
2012-08-15 21:27               ` tlaronde
2012-08-16  3:47                 ` Bakul Shah
2012-08-16  5:34                   ` tlaronde
2012-08-16 13:40                     ` erik quanstrom
2012-08-16 15:41                       ` tlaronde
2012-08-16 16:06                         ` erik quanstrom
2012-08-16 16:28                           ` tlaronde
2012-08-16 15:59                       ` Bakul Shah
2012-08-16 16:31                         ` tlaronde
2012-08-16 16:48                         ` Burton Samograd
2012-08-16 17:02                 ` Eugene Gorodinsky
2012-08-16 19:48                   ` tlaronde
2012-08-16 20:11                     ` erik quanstrom
2012-08-17  6:48                       ` tlaronde
2012-08-17  7:48                         ` Lucio De Re
2012-08-20 15:17                           ` tlaronde

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=20120803192544.GA4961@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).