From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 25 Jul 2012 12:24:22 +1200 From: Andy Elvey To: 9fans@9fans.net Message-id: <500F3CB6.105@paradise.net.nz> MIME-version: 1.0 Content-type: multipart/alternative; boundary=------------040504000209050601070609 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 Subject: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4a4d4f2-ead7-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --------------040504000209050601070609 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everyone - I'm a first-timer here - I'm thinking of doing a "public domain" implementation (in C) of 9P. I've seen the large listing (on the cat-v site) of existing 9P implementations which are under various licenses, and so in thinking about where those people obtained the required information from, the following questions came to mind - a) The information *must* have been obtained from the Plan 9 technical docs (specification papers) or the Plan 9 man pages. Can the information in either of these be regarded as being "public domain"? (It would seem to be, given the number of different licenses of the various implementations. They could surely not have taken LPL-licensed code and then converted it to GPL, BSD, MIT......? It would seem that the proliferation of licenses could only be done if the original source of the information was "public domain". ) b) If the answer to (a) is "yes" - does that include the source-code shown in those papers (and the man pages)? I've seen the "public domain" implementation of 9P in Python (by Tim Newsham), so I assume he got the required information from the places I've mentioned. Thanks for your time - looking forward to your replies. - Andy --------------040504000209050601070609 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everyone - I'm a first-timer here -

I'm thinking of doing a "public domain" implementation (in C) of 9P. I've seen the large listing (on the cat-v site) of existing 9P implementations which are under various licenses, and so in thinking about where those people obtained the required information from, the following questions came to mind -

a) The information *must* have been obtained from the Plan 9 technical docs (specification papers) or the Plan 9 man pages. Can the information in either of these be regarded as being "public domain"? (It would seem to be, given the number of different licenses of the various implementations. They could surely not have taken LPL-licensed code and then converted it to GPL, BSD, MIT......?

It would seem that the proliferation of licenses could only be done if the original source of the information was "public domain". )

b) If the answer to (a) is "yes" - does that include the source-code shown in those papers (and the man pages)?

I've seen the "public domain" implementation of 9P in Python (by Tim Newsham), so I assume he got the required information from the places I've mentioned.

Thanks for your time - looking forward to your replies.
- Andy

--------------040504000209050601070609-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <500F3CB6.105@paradise.net.nz> References: <500F3CB6.105@paradise.net.nz> Date: Wed, 25 Jul 2012 04:18:53 +0200 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4af8c26-ead7-11e9-9d60-3106f5b1d025 nobody here's a lawyer. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <500F3CB6.105@paradise.net.nz> Date: Tue, 24 Jul 2012 20:47:37 -0600 Message-ID: From: andrey mirtchovski To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4b70096-ead7-11e9-9d60-3106f5b1d025 I'm not a lawyer but I play one in comedy clubs. The first implementation of 9p came about long before Plan 9 had a free (as in rms) license. Nobody got sued, nobody died, although a few bystanders were maimed. My advice as your lawyer [in comedy] would be to go nuts and do whatever you want. The documentation[1] is a good place to start if you don't want to look at any source (no license required to see that!), and if you want to cover all corner cases, a running Plan 9 kernel is a good client/server to test against. ---- 1: http://plan9.bell-labs.com/sys/man/5/INDEX.html From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <500F3CB6.105@paradise.net.nz> Date: Tue, 24 Jul 2012 20:52:12 -0600 Message-ID: From: andrey mirtchovski To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4bd681e-ead7-11e9-9d60-3106f5b1d025 > (no license required to see > that!) there is, however, a copyright link at the bottom of each man page. as your lawyer [in comedy] i advise you to click it. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 25 Jul 2012 15:31:34 +1200 From: Andy Elvey In-reply-to: To: 9fans@9fans.net Message-id: <500F6896.4010605@paradise.net.nz> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_9wa31UgkMTMERMgd2EZVkQ)" References: <500F3CB6.105@paradise.net.nz> User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4c2ed84-ead7-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --Boundary_(ID_9wa31UgkMTMERMgd2EZVkQ) Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT Hi Andrey - thanks for your reply! On 25/07/12 14:47, andrey mirtchovski wrote: > I'm not a lawyer but I play one in comedy clubs. The first > implementation of 9p came about long before Plan 9 had a free (as in > rms) license. Nobody got sued, nobody died, although a few bystanders > were maimed. Interesting. It's good to find out a bit of the history behind 9p. > > My advice as your lawyer [in comedy] would be to go nuts and do > whatever you want. The documentation[1] is a good place to start if > you don't want to look at any source (no license required to see > that!), and if you want to cover all corner cases, a running Plan 9 > kernel is a good client/server to test against. > > ---- > 1: http://plan9.bell-labs.com/sys/man/5/INDEX.html Thanks for that! I'll check that page out too. Btw - I clicked on the "copyright" link at the bottom, but the link is dead - nothing but a 404 page error. In looking at Tim Newsham's P9.py, he has a comment in the code - "9P protocol implementation as documented in plan9 intro(5) and ." ( I would likely be even more cautious and avoid looking at any header files if possible. ) Thanks again, Andrey - you've been very helpful! - Andy --Boundary_(ID_9wa31UgkMTMERMgd2EZVkQ) Content-type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Andrey - thanks for your reply!=C2=A0

On 25/07/12 14:47, andrey mirtchovski wrote:

I'm not a lawyer but I play one in comedy clubs. The=
 first
implementation of 9p came about long before Plan 9 had a free (as in
rms) license. Nobody got sued, nobody died, although a few bystanders
were maimed.

Interesting. It's good to find out a bit of the history behind 9p. =C2= =A0


My advice as your lawyer [in comedy] would be to go nuts and do
whatever you want. The documentation[1] is a good place to start if
you don't want to look at any source (no license required to see
that!), and if you want to cover all corner cases, a running Plan 9
kernel is a good client/server to test against.

----
1: http://plan9.bell-labs.com/sys/man/5/INDEX.html=

Thanks for that!=C2=A0 I'll check that page out too.=C2=A0
Btw - I clicked on the "copyright" link at the bottom, but the link is dead - nothing but a 404 page error.

In looking at Tim Newsham's P9.py, he has a comment in the code - "9P protocol implementation as documented in plan9 intro(5) and <fcall.h>."=C2=A0
( I would likely be even more cautious and avoid looking at any header files if possible. )=C2=A0
Thanks again, Andrey - you've been very helpful!=C2=A0
- Andy =C2=A0 =C2=A0
--Boundary_(ID_9wa31UgkMTMERMgd2EZVkQ)-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Tue, 24 Jul 2012 23:58:08 -0400 To: 9fans@9fans.net Message-ID: <87b3013b3f0007eb3ab5e63f56c3ce47@brasstown.quanstro.net> In-Reply-To: <500F6896.4010605@paradise.net.nz> References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4c8cd9e-ead7-11e9-9d60-3106f5b1d025 > In looking at Tim Newsham's P9.py, he has a comment in the code - "9P > protocol implementation as documented in plan9 intro(5) and ." > ( I would likely be even more cautious and avoid looking at any header > files if possible. ) > Thanks again, Andrey - you've been very helpful! section 5 of the manual should be a complete description of the protocol. the comment might be slightly misleading. that not withstanding, ianal, but my understanding is that header files, are considered similar to facts under copyright law, and therefore not copyrightable. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <500F6896.4010605@paradise.net.nz> References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> From: John Floren Date: Tue, 24 Jul 2012 21:06:07 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4ce6524-ead7-11e9-9d60-3106f5b1d025 On Tue, Jul 24, 2012 at 8:31 PM, Andy Elvey wrote: > Hi Andrey - thanks for your reply! > > On 25/07/12 14:47, andrey mirtchovski wrote: > > I'm not a lawyer but I play one in comedy clubs. The first > implementation of 9p came about long before Plan 9 had a free (as in > rms) license. Nobody got sued, nobody died, although a few bystanders > were maimed. > > Interesting. It's good to find out a bit of the history behind 9p. > > My advice as your lawyer [in comedy] would be to go nuts and do > whatever you want. The documentation[1] is a good place to start if > you don't want to look at any source (no license required to see > that!), and if you want to cover all corner cases, a running Plan 9 > kernel is a good client/server to test against. > > ---- > 1: http://plan9.bell-labs.com/sys/man/5/INDEX.html > > Thanks for that! I'll check that page out too. > Btw - I clicked on the "copyright" link at the bottom, but the link is dead > - nothing but a 404 page error. > > In looking at Tim Newsham's P9.py, he has a comment in the code - "9P > protocol implementation as documented in plan9 intro(5) and ." > ( I would likely be even more cautious and avoid looking at any header files > if possible. ) > Thanks again, Andrey - you've been very helpful! > - Andy Just write the code, nobody cares. The manual pages define an interface, and you're going to implement it. The manual pages are copyrighted, sure, because they're written works and are automatically protected by copyright. Besides the recent Google vs. Oracle fiasco, I can't think of a time an open-source project had legal problems by writing new code to implement an API. And, based on a brief reading of http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as though a US judge has ruled that an API is not subject to copyright; if you implement the 9P API, you should be fine. Also, since you're doing a free reimplementation of code which is currently available free to everyone by the creators (Lucent), I have a hard time figuring out exactly what basis they'd have for a lawsuit. john From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <500F6896.4010605@paradise.net.nz> References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> Date: Tue, 24 Jul 2012 22:08:14 -0600 Message-ID: From: andrey mirtchovski To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4d84422-ead7-11e9-9d60-3106f5b1d025 > Btw - I clicked on the "copyright" link at the bottom, but the link is dead > - nothing but a 404 page error. that's the joke :) plan9 has been considered a dead operating system for a long time. from my (admittedly little) experience with 9p implementations, the ones done "outside" of plan9 code influence were done based on the man pages and then tested against the plan9 kernel driver. the implementations that came after Lucent Public Licence 1.0.2 (the OSS-approved one) all share a few similarities, mostly in structs. I think they all "gleaned" from Russ Cox's plan9port C code which may have been used as a reference. the 9p code in the linux kernel, i believe, doesn't share similarities in its data structs with plan9 (compare p9_fcall with fcall). I think Tim's py9p came after the OSS approval of the Lucent licence. I can tell you that Tim's original implementation used an unmarshalling routine that was definitely not derived from read9pmsg. it was (is) very python-y. From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 25 Jul 2012 00:10:52 -0400 To: 9fans@9fans.net Message-ID: <4bf128a00f10bea623861cc44e9b9ff4@brasstown.quanstro.net> In-Reply-To: References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4dde1b6-ead7-11e9-9d60-3106f5b1d025 > that's the joke :) plan9 has been considered a dead operating system > for a long time. ssssh. don't tell my employer. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> <4bf128a00f10bea623861cc44e9b9ff4@brasstown.quanstro.net> In-Reply-To: <4bf128a00f10bea623861cc44e9b9ff4@brasstown.quanstro.net> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Message-Id: <6CB4BEDB-45E9-48C8-8AC5-777F0E9F62EE@gmail.com> Cc: "9fans@9fans.net" <9fans@9fans.net> From: Skip Tavakkolian Date: Tue, 24 Jul 2012 21:33:12 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4e40aaa-ead7-11e9-9d60-3106f5b1d025 For a dead OS, Plan 9 sure gets around ;) Plan 9, a nurse-log of modern computing. -Skip On Jul 24, 2012, at 9:10 PM, erik quanstrom wrote: >> that's the joke :) plan9 has been considered a dead operating system >> for a long time. > > ssssh. don't tell my employer. > > - erik > From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <6CB4BEDB-45E9-48C8-8AC5-777F0E9F62EE@gmail.com> References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> <4bf128a00f10bea623861cc44e9b9ff4@brasstown.quanstro.net> <6CB4BEDB-45E9-48C8-8AC5-777F0E9F62EE@gmail.com> From: Jens Staal Date: Wed, 25 Jul 2012 07:09:48 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a4ff2e66-ead7-11e9-9d60-3106f5b1d025 2012/7/25 Skip Tavakkolian : > For a dead OS, Plan 9 sure gets around ;) > > Plan 9, a nurse-log of modern computing. > > -Skip > > On Jul 24, 2012, at 9:10 PM, erik quanstrom wrote: > >>> that's the joke :) plan9 has been considered a dead operating system >>> for a long time. >> >> ssssh. don't tell my employer. >> >> - erik >> > It must be Eros stimulating its pituitary and pineal glands. ;) (http://en.wikipedia.org/wiki/Plan_9_from_Outer_Space) From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 25 Jul 2012 18:01:17 +1200 From: Andy Elvey In-reply-to: To: 9fans@9fans.net Message-id: <500F8BAD.3020102@paradise.net.nz> MIME-version: 1.0 Content-type: multipart/alternative; boundary=------------050902070409040608030809 References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a50fdd88-ead7-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --------------050902070409040608030809 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 25/07/12 16:06, John Floren wrote: (snip) > Just write the code, nobody cares. The manual pages define an > interface, and you're going to implement it. The manual pages are > copyrighted, sure, because they're written works and are automatically > protected by copyright. Besides the recent Google vs. Oracle fiasco, I > can't think of a time an open-source project had legal problems by > writing new code to implement an API. And, based on a brief reading of > http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as though a > US judge has ruled that an API is not subject to copyright; if you > implement the 9P API, you should be fine. Also, since you're doing a > free reimplementation of code which is currently available free to > everyone by the creators (Lucent), I have a hard time figuring out > exactly what basis they'd have for a lawsuit. john Hi John - thanks for that. Thanks also to everyone who has commented in this thread - you've been very helpful! This is one of the most helpful lists that I've been on. This feedback is very useful as a guide to how to proceed. Although I'm not running Plan 9 at present (I'm on Linux), I'm very impressed with its elegance. Everything from kbdfs to the plumber to the Venti filesystem - it's all beautifully thought-out. The way that Venti uses SHA1 hashes to store data reminds me a lot of Git (which I also really like - there's another elegantly designed bit of software). Thanks again, all - bye for now :) - Andy --------------050902070409040608030809 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 25/07/12 16:06, John Floren wrote:
(snip)

Just write the code, nobody cares. The manual pages define an interface, and you're going to implement it. The manual pages are copyrighted, sure, because they're written works and are automatically protected by copyright. Besides the recent Google vs. Oracle fiasco, I can't think of a time an open-source project had legal problems by writing new code to implement an API. And, based on a brief reading of http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as though a US judge has ruled that an API is not subject to copyright; if you implement the 9P API, you should be fine. Also, since you're doing a free reimplementation of code which is currently available free to everyone by the creators (Lucent), I have a hard time figuring out exactly what basis they'd have for a lawsuit. john

Hi John - thanks for that.
Thanks also to everyone who has commented in this thread - you've been very helpful! This is one of the most helpful lists that I've been on.
This feedback is very useful as a guide to how to proceed.

Although I'm not running Plan 9 at present (I'm on Linux), I'm very impressed with its elegance. Everything from kbdfs to the plumber to the Venti filesystem - it's all beautifully thought-out. The way that Venti uses SHA1 hashes to store data reminds me a lot of Git (which I also really like - there's another elegantly designed bit of software).
Thanks again, all - bye for now :)
- Andy

--------------050902070409040608030809-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <500F8BAD.3020102@paradise.net.nz> References: <500F3CB6.105@paradise.net.nz> <500F6896.4010605@paradise.net.nz> <500F8BAD.3020102@paradise.net.nz> Date: Wed, 25 Jul 2012 07:14:59 -0700 Message-ID: From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=e89a8ffbae69ae98b504c5a81a26 Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"? Topicbox-Message-UUID: a51420f0-ead7-11e9-9d60-3106f5b1d025 --e89a8ffbae69ae98b504c5a81a26 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jul 24, 2012 at 11:01 PM, Andy Elvey wrote: > On 25/07/12 16:06, John Floren wrote: > (snip) > > Just write the code, nobody cares. The manual pages define an interface, > and you're going to implement it. The manual pages are copyrighted, sure, > because they're written works and are automatically protected by copyright. > Besides the recent Google vs. Oracle fiasco, I can't think of a time an > open-source project had legal problems by writing new code to implement an > API. And, based on a brief reading of > http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as though a US > judge has ruled that an API is not subject to copyright; if you implement > the 9P API, you should be fine. Also, since you're doing a free > reimplementation of code which is currently available free to everyone by > the creators (Lucent), I have a hard time figuring out exactly what basis > they'd have for a lawsuit. john > > Hi John - thanks for that. > Thanks also to everyone who has commented in this thread - you've been > very helpful! This is one of the most helpful lists that I've been on. > This feedback is very useful as a guide to how to proceed. > > Although I'm not running Plan 9 at present (I'm on Linux), I'm very > impressed with its elegance. Everything from kbdfs to the plumber to the > Venti filesystem - it's all beautifully thought-out. The way that Venti > uses SHA1 hashes to store data reminds me a lot of Git (which I also really > like - there's another elegantly designed bit of software). > Thanks again, all - bye for now :) > - Andy > > Linux of course has v9fs which is a 9P implementation in the kernel. --e89a8ffbae69ae98b504c5a81a26 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Jul 24, 2012 at 11:01 PM, Andy E= lvey <andy.elvey@paradise.net.nz> wrote:
=20 =20 =20

On 25/07/12 16:06, John Floren wrote:
(snip)

Just write the code, nobody cares. The manual pages define an interface, and you're going to implement it. The manual pages are copyrighted, sure, because they're written works and are automatically protected by copyright. Besides the recent Google vs. Oracle fiasco, I can't think of a time an open-source project had legal problems by writing new code to implement an API. And, based on a brief reading of http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as tho= ugh a US judge has ruled that an API is not subject to copyright; if you implement the 9P API, you should be fine. Also, since you're doin= g a free reimplementation of code which is currently available free to everyone by the creators (Lucent), I have a hard time figuring out exactly what basis they'd have for a lawsuit. john

Hi John - thanks for that.=A0
Thanks also to everyone who has commented in this thread - you've been very helpful!=A0 This is one of the most helpful lists that I'= ve been on.
This feedback is very useful as a guide to how to proceed.

Although I'm not running Plan 9 at present (I'm on Linux), I= 9;m very impressed with its elegance. Everything from kbdfs to the plumber to the Venti filesystem - it's all beautifully thought-out.=A0 The way that Venti uses SHA1 hashes to store data reminds me a lot of Git (which I also really like - there's another elegantly designed bit of software).=A0 =A0
Thanks again, all - bye for now :) =A0
- Andy=A0
=A0

Linux of co= urse has v9fs which is a 9P implementation in the kernel. =A0=A0

--e89a8ffbae69ae98b504c5a81a26--