From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2A42D5A6-C7C1-4E40-A9B0-4E8F6591E079@bitblocks.com> References: <2A42D5A6-C7C1-4E40-A9B0-4E8F6591E079@bitblocks.com> From: Charles Forsyth Date: Thu, 23 Feb 2017 09:00:51 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a1141068c985e3405492ed9a6 Subject: Re: [9fans] Upspin - a respin of 9p? Topicbox-Message-UUID: b4fc772c-ead9-11e9-9d60-3106f5b1d025 --001a1141068c985e3405492ed9a6 Content-Type: text/plain; charset=UTF-8 I don't think it's a reworking of 9P. It's closer to an older style of distributed file system, closer to Amoeba's or the Cambridge Distributed System, and using full-content storage operations on content accessed through a separate and global name service. 9P (and relatives) allow a huge assortment of surprisingly different service types to be represented and accessed in a uniform way, where conventional file storage is easily the least interesting service. (That isn't a criticism: both this and 9P-like things have their place.) --001a1141068c985e3405492ed9a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I don't think it's a re= working of 9P.
It's closer to an older = style of distributed file system, closer to Amoeba's or the Cambridge D= istributed System,
and using full-content s= torage operations on content accessed through a separate and global name se= rvice.
9P (and relatives) allow a huge asso= rtment of surprisingly different service types to be represented and access= ed in a uniform way,
where conventional fil= e storage is easily the least interesting service.
(That isn't a criticism: both this and 9P-like things have thei= r place.)

--001a1141068c985e3405492ed9a6--