From: Skip Tavakkolian <skip.tavakkolian@gmail.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 11:58:08 -0700 [thread overview]
Message-ID: <CAJSxfmKN55K7URLEUw+vA_YSeSySVF+V7YAktMvzxPvCbuVptg@mail.gmail.com> (raw)
In-Reply-To: <20120803171847.GA2720@polynum.com>
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).
-Skip
On Fri, Aug 3, 2012 at 10:18 AM, <tlaronde@polynum.com> wrote:
> Hello,
>
> This is mainly a theoretical question.
>
> While playing with the representation of mathematical definitions as a
> file hierarchy (at dot you find a DESC or whatever named file with the
> description, and the subdirs are simply more restrictive instances of
> the thing; say : collection -> magma -> monoïde -> group etc.), it is
> soon obvious that a filesystem is a one dimension thing: you only follow
> one string. Multiple "parents" at the same level are not there.
>
> One could trick partly using hard or soft links. But with always the
> same problem: who is dot-dot, in a case where multiple parents are here?
> And multiple parents are not, to my knowledge, supported by kernel
> filesystem code. Manipulating the namespace is not the same.
>
> Has someone ever played with the notion of a multidimensional
> filesystem, where '/' is the origin, the nodes would be some
> representation of (a, b, c,...) (even negatives perhaps), each node
> having a name (user defined one by the way), and if
> a node is, say (3, 0, 1,...) this means that it is to be found as the
> third subdir of the (1, 0, 0,...) path etc., (In this scheme, if there
> is no link (no path) from another notion, it is another dimension).
>
> Just for intellectual curiosity.
>
> Best,
> --
> Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
> http://www.kergis.com/
> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
>
next prev parent reply other threads:[~2012-08-03 18:58 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 [this message]
2012-08-03 19:25 ` tlaronde
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=CAJSxfmKN55K7URLEUw+vA_YSeSySVF+V7YAktMvzxPvCbuVptg@mail.gmail.com \
--to=skip.tavakkolian@gmail.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).