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 21:06:11 -0700 [thread overview]
Message-ID: <20120816040611.9D9EEB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 15 Aug 2012 21:38:43 EDT." <5aa378b509888aef72837f09e32a2c71@kw.quanstro.net>
On Wed, 15 Aug 2012 21:38:43 EDT erik quanstrom <quanstro@quanstro.net> 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 it that way! Regardless, both can be used to
distribute files.
> 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 be part of a purpose-built fs.
How would this work? Someone has to map "/net/my-nodes/foo" to
a set of files. Either a program iterates over the list or you
push this list processing into the "purpose built" filesystem.
[Actually the latter is what I was thinking of -- A "9p*"
protocol would return a list of file handles, and "rc*" would
be an APLish version of rc]
next prev parent reply other threads:[~2012-08-16 4:06 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
2012-08-16 1:38 ` erik quanstrom
2012-08-16 4:06 ` Bakul Shah [this message]
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=20120816040611.9D9EEB827@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).