From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Multi-dimensional filesystem
Date: Wed, 15 Aug 2012 14:00:03 -0700 [thread overview]
Message-ID: <20120815210003.25E16B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 15 Aug 2012 16:17:28 EDT." <cf80dc712aed825628914e114fd9a52e@coraid.com>
On Wed, 15 Aug 2012 16:17:28 EDT erik quanstrom <quanstro@labs.coraid.com> 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 to a list of network nodes -- so something like
> >
> > echo "date" > /net/my-nodes/foo
> > chmod +x /net/my-nodes/foo
> > /net/my-nodes/foo
>
> one would think that a distributing file server would be
> a better abstraction as the normal tools could be brought
> to bear on the problem.
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. There are some
graph languages that could possibly map here.
What is a "distributing" file server? If you mean something
like cxfs, luster, glusterfs, ceph, etc they wouldn't do the
same thing. The above would in fact be kind of a distributed
filesystem!
next prev parent reply other threads:[~2012-08-15 21:00 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
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 [this message]
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=20120815210003.25E16B827@mail.bitblocks.com \
--to=bakul@bitblocks.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).