From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 15 Aug 2012 21:38:43 -0400 To: 9fans@9fans.net Message-ID: <5aa378b509888aef72837f09e32a2c71@kw.quanstro.net> In-Reply-To: <20120815210003.25E16B827@mail.bitblocks.com> References: <20120803171847.GA2720@polynum.com> <501D12A1.1060906@yahoo.fr> <20120804152016.GB433@polynum.com> <20120805173639.GA395@polynum.com> <20120815173327.GA424@polynum.com> <20120815200949.4628BB85B@mail.bitblocks.com> <20120815210003.25E16B827@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Multi-dimensional filesystem Topicbox-Message-UUID: a9d82302-ead7-11e9-9d60-3106f5b1d025 > 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! 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. 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. - erik