I just had this forwarded to me, and for all that it uses the L-word,
it's potentially good news for us too.  As I type, I'm fetching the
.tar.gz, just in case it vanishes; do we perhaps want to do some
cleanrooming ourselves?

It's not clear to me to what extent the stuff in the .tar.gz is covered
by the plan9 license; I haven't yet unpacked the tar and looked for
copyright license terms.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

> Date: Mon, 20 Dec 1999 11:55:39 -0500
> From: Nick Poolos <poolos@net.ohio-state.edu>
> To: developers@black.linux-m68k.org
> Subject: [black-linux] Re: Black Christmas
> X-Mailer: Mutt 0.94.15i
> In-Reply-To: <385D055C.A906A1DE@hursley.ibm.com>; from David Griffiths on Sun, Dec 19, 1999 at 04:18:36PM +0000
> X-Mailer: Mutt
> X-Editor: Emacs
> X-archive-position: 77
> X-listar-version: Listar v0.128a
> Errors-to: black-linux-bounce@iaeste.or.at
> X-original-sender: poolos@net.ohio-state.edu
> Precedence: bulk
> X-list: black-linux
> 
> Be _very_ careful looking at this source.  The terms of the plan9 shrinkwrap license are here:
> 
> 	http://plan9.bell-labs.com/plan9/shrink.html
> 
> If any use of this code is going to be made we need to implement clean room proceedure NOW.....
> 
> Do _not_ download or look at the tarball if you plan on writing the linux code.  There are some very nasty derivative works clauses in the Plan9 license. Not to mention that Plan9 is commercially licensed code, and passing around copies will be questionable.  
> 
> What we need are one or two people to document the plan9 stuff and feed those docs to a couple of other people.  we probably should post all docs and other questions either on this list or another public forum/list.  
> 
> If anyone knows an attorney and could get a little advice in how to proceed that would be great.
> 
> Also I highly recommend that if we proceed the port should probably start from scratch.  the current NeXT head.s has some issues.  Taking the current head.s etc up to a modern kernel (2.3.xx) will be difficult.  This is because the current code does not have a boot loader, head.s take s the PROM structs and bashes up the MMU etc.  This should occur in a boot loader, thus leaving head.s much cleaner and easier to deal with.
> 
> --
> Nick Poolos
> poolos@net.ohio-state.edu  
> 
> * David Griffiths (dgriff@hursley.ibm.com) [991219 11:39]:
> > Here is a tar file containing the NeXT-specific parts of Plan 9. Should
> > contain everything you need to complete a port of Linux. Although I made
> > a start on the Linux port back in the summer when things were quiet, I
> > just don't have time any more. Would still love to see Linux on my Cube
> > though!
> > 
> > http://www.prim.demon.co.uk/plan9.tar.gz
> > 
> > Happy Christmas!
> > 
> > Dave
> > ==============================================================
> >     write to the list at: developers@black.linux-m68k.org
> >     to join send mail to developers-request@black.linux-m68k.org;
> > subscribe
> >     in the body.
> >     please don't forget to send an introduction of yourself to the list
> >     to leave: 
> > echo unsubscribe | mail developers-request@black.linux-m68k.org
> >     find our homepage at: http://www.black.linux-m68k.org/
> > ==============================================================
> ==============================================================
>     write to the list at: developers@black.linux-m68k.org
>     to join send mail to developers-request@black.linux-m68k.org;
> subscribe
>     in the body.
>     please don't forget to send an introduction of yourself to the list
>     to leave: 
> echo unsubscribe | mail developers-request@black.linux-m68k.org
>     find our homepage at: http://www.black.linux-m68k.org/
> ==============================================================
> 
> 
> ----- End forwarded message -----
>