From: andrey mirtchovski <mirtchovski@gmail.com>
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"?
Date: Tue, 24 Jul 2012 22:08:14 -0600 [thread overview]
Message-ID: <CAK4xykXO3AGWN_=LjeCOdNXsP1pq-6iy+M6Srm6ch4BrAz01sA@mail.gmail.com> (raw)
In-Reply-To: <500F6896.4010605@paradise.net.nz>
> 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.
next prev parent reply other threads:[~2012-07-25 4:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 0:24 Andy Elvey
2012-07-25 2:18 ` hiro
2012-07-25 2:47 ` andrey mirtchovski
2012-07-25 2:52 ` andrey mirtchovski
2012-07-25 3:31 ` Andy Elvey
2012-07-25 3:58 ` erik quanstrom
2012-07-25 4:06 ` John Floren
2012-07-25 6:01 ` Andy Elvey
2012-07-25 14:14 ` David Leimbach
2012-07-25 4:08 ` andrey mirtchovski [this message]
[not found] ` <CAK4xykXO3AGWN_=LjeCOdNXsP1pq-6iy+M6Srm6ch4BrAz01sA@mail.gmail.c>
2012-07-25 4:10 ` erik quanstrom
2012-07-25 4:33 ` Skip Tavakkolian
2012-07-25 5:09 ` Jens Staal
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='CAK4xykXO3AGWN_=LjeCOdNXsP1pq-6iy+M6Srm6ch4BrAz01sA@mail.gmail.com' \
--to=mirtchovski@gmail.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).