On Fri, Aug 17, 2012 at 09:48:33AM +0200, Lucio De Re wrote:
>
> The question here is how to enhance the Unix-like hierarchical
> directory to embrace multi-dimensionality. I have no doubt that the
> changes to 9P that will almost certainly be required for this will be
> fairly obvious and from t
> The
> "getting dot-dot right" is precisely the problem that there are
> multiple paths, and only one is valid for a classical dir tree and
> you got to follow this one correct path back. Here, this multiplicity
> is simultaneously valid, and all the paths are the correct answer.
The question her
On Thu, Aug 16, 2012 at 04:11:11PM -0400, erik quanstrom wrote:
> > I think you missed the point. What I have given is an example, what
> > indeed made me wonder, initially, about a way to simply store
> > definitions as a text file, the relationships between the notions
> > being described by a di
> I think you missed the point. What I have given is an example, what
> indeed made me wonder, initially, about a way to simply store
> definitions as a text file, the relationships between the notions
> being described by a directory structure. It was obvious rapidly
> that this won't do in a clas
On Thu, Aug 16, 2012 at 08:02:52PM +0300, Eugene Gorodinsky wrote:
> >
> > First one, related to what I was wandering about, is mathematical
> > definitions and relationships. Take the picture of the first volume of
> > van der Waerden's Albebra (I have the german edition and will keep the
> > germ
>
> First one, related to what I was wandering about, is mathematical
> definitions and relationships. Take the picture of the first volume of
> van der Waerden's Albebra (I have the german edition and will keep the
> german words). We speak about links between notions presented in a
> linear order
> It pretty much has to. Consider what happens when you do something like
>
> % x=`{pwd}
> % bind /sys/src tmp
> % cd tmp
> % cd ..
>
> This gets you back to $x. If you leave ".." upto the fileserver, you'd get
> back to /sys not $x. The server can't know the right context.
I thought this probl
On Thu, Aug 16, 2012 at 08:59:01AM -0700, Bakul Shah wrote:
> On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom
> wrote:
> > > What is more bizarre, with my scheme, is how to implement the meaning
> > > of ".."? If classical clients have to be able to be used, the server
> > > must create a fake n
On Thu, Aug 16, 2012 at 12:06:40PM -0400, erik quanstrom wrote:
>
> >
> > Except by allowing a new syntax .../{a,b,c,d}/foo meaning that foo has
> > a, b, c and d as parents, the only way I see things working with the
> > utilities and the ".." treatment is to insert a special name ensuring
> > t
On Thu Aug 16 11:44:01 EDT 2012, tlaro...@polynum.com wrote:
> On Thu, Aug 16, 2012 at 09:40:22AM -0400, erik quanstrom wrote:
> > > What is more bizarre, with my scheme, is how to implement the meaning
> > > of ".."? If classical clients have to be able to be used, the server
> > > must create a f
On Thu, 16 Aug 2012 09:40:22 EDT erik quanstrom wrote:
> > What is more bizarre, with my scheme, is how to implement the meaning
> > of ".."? If classical clients have to be able to be used, the server
> > must create a fake name (as the penultimate component of the
> > dirpath), that triggers th
On Thu, Aug 16, 2012 at 09:40:22AM -0400, erik quanstrom wrote:
> > What is more bizarre, with my scheme, is how to implement the meaning
> > of ".."? If classical clients have to be able to be used, the server
> > must create a fake name (as the penultimate component of the
> > dirpath), that trig
> > and as such, i was thinking of a server that simply distributed requests
> > among a set of servers. so that
> >
> > > > > echo "date" > /net/my-nodes/foo
> > > > > chmod +x /net/my-nodes/foo
> >
> > would work with the normal tools on a normal kernel. all the distribution
> > would
> What is more bizarre, with my scheme, is how to implement the meaning
> of ".."? If classical clients have to be able to be used, the server
> must create a fake name (as the penultimate component of the
> dirpath), that triggers the correct answer from the server.
see defmnt.c:/^fixdotdotname f
On Wed, Aug 15, 2012 at 08:47:47PM -0700, Bakul Shah wrote:
>
> > 2) In 9P, the ".." if I'm not mistaken is not here. One can request a
> > file, or go back to the previous one. The ".." including "path removing"
> > is not implemented in 9P if I read correctly the manpage. So a client
> > can spe
On Wed, 15 Aug 2012 21:38:43 EDT erik quanstrom wrote:
>
> i was thinking of file server in the traditional (ahem) plan 9 sense,
> a network service that responds to 9p rather than a traditional (boring)
> unix-style store.
To me the plan9 model is the "boring" one. Boringly simple.
And I like
On Wed, 15 Aug 2012 23:27:34 +0200 tlaro...@polynum.com wrote:
>
> I will give two (DeLuxe(R) version!) examples.
Thanks. Sounds like you are taking about IS-A and HAS-A
relationships.
> 2) In 9P, the ".." if I'm not mistaken is not here. One can request a
> file, or go back to the previous one
> I was just exploring the APLish nature of the idea. I used
> shell syntax to get the idea across -- here my-nodes would map
> to a set of fileserver nodes that interpret the remaining path
> so this path actually maps to a whole bunch of files. No idea
> if this is better, worse or even sensible
On Wed, Aug 15, 2012 at 01:09:49PM -0700, Bakul Shah wrote:
>
> Sounds like you want to represent a node with a directory,
> that has a "content" file that stores content associated with
> this node and a bunch of links to other nodes. You are most
> interested in parent/child relationships so fo
On Wed, 15 Aug 2012 16:17:28 EDT erik quanstrom
wrote:
> > x = open("a/b/c", mode)
> >
> > can yield a vector of file descriptors! Leaving component
> > interpretation to the current node makes this a very dynamic
> > and powerful system (for example, one can think of a node that
> > maps
> x = open("a/b/c", mode)
>
> can yield a vector of file descriptors! Leaving component
> interpretation to the current node makes this a very dynamic
> and powerful system (for example, one can think of a node that
> maps to a list of network nodes -- so something like
>
> echo "date"
On Wed, 15 Aug 2012 19:33:27 +0200 tlaro...@polynum.com wrote:
>
> The main differences from what I have in mind are:
>
> 1) There is no general relational database concept: the relationships of
> the "records" (files, that can have both a text content [the definition
> in my example] and be a d
On Wed, Aug 15, 2012 at 07:04:28PM +0300, Eugene Gorodinsky wrote:
> I'm sure I must not understand the problem fully and am confused because of
> that, but how is this idea of multidimensionality different from a
> relational filesystem approach such as befs (
> http://www.nobius.org/~dbg/practica
I'm sure I must not understand the problem fully and am confused because of
that, but how is this idea of multidimensionality different from a
relational filesystem approach such as befs (
http://www.nobius.org/~dbg/practical-file-system-design.pdf)?
2012/8/5
> On Sun, Aug 05, 2012 at 11:29:19AM
On Sun, Aug 05, 2012 at 11:29:19AM -0400, Charles Forsyth wrote:
> There is also http://lsub.org/iwp9/cready/abheyshahplan9.pdf
Thank you! Indeed, this is related.
--
Thierry Laronde
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6
There is also http://lsub.org/iwp9/cready/abheyshahplan9.pdf
On Sat, Aug 04, 2012 at 02:16:33PM +0200, Nicolas Bercher wrote:
>
> As far as I understand, it seems you are interested in the idea of views
> over your files. Something that has been approached as "non-hierarchical
> file systems". But the complexity of handling such graphs often seems to
> be t
On Sat, Aug 04, 2012 at 01:56:07PM +0300, Aram H?v?rneanu wrote:
> I'm pretty sure there's an isomorphism between your multidimensional
> filesystem and the set of potential namespaces. A dimension in your
> multidimensional fileysystem is just an arbitrary set of filesystems
> bounded in a particu
On 03/08/2012 19:18, tlaro...@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
i
I'm pretty sure there's an isomorphism between your multidimensional
filesystem and the set of potential namespaces. A dimension in your
multidimensional fileysystem is just an arbitrary set of filesystems
bounded in a particular namespace...
--
Aram Hăvărneanu
Hello,
On Fri, Aug 03, 2012 at 05:08:52PM -0400, Burton Samograd wrote:
>
> > Has someone ever played with the notion of a multidimensional filesystem
>
> David Korn did some research on a 3d file system called 3d:
>
> David G. Korn, Eduardo Krell, The 3-D File System, pp147-156, USENIX
> Conf
lan 9 from Bell Labs
Subject: Re: [9fans] Multi-dimensional filesystem
On Fri, Aug 03, 2012 at 05:08:52PM -0400, Burton Samograd wrote:
>
> This e-mail, including accompanying communications and attachments, is
> strictly confidential and only for the intended recipient. Any retention, u
On Fri, Aug 03, 2012 at 05:08:52PM -0400, Burton Samograd wrote:
>
> This e-mail, including accompanying communications and attachments, is
> strictly confidential and only for the intended recipient. Any retention, use
> or disclosure not expressly authorised by Markit is prohibited. This email
> Has someone ever played with the notion of a multidimensional filesystem
David Korn did some research on a 3d file system called 3d:
David G. Korn, Eduardo Krell, The 3-D File System, pp147-156, USENIX Conference
Proceedings, Summer 1989, Baltimore, MD
And also at behind a paywall:
http://
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 t
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
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 ->
37 matches
Mail list logo
