Subject: NetBSD Copyright (Was: Re: Last chance: Copyrights is OK ?)
To: NetBSD current users <current-users@netbsd.org>
From: Eric Delcamp <e.delcamp@wanadoo.fr>
List: tech-kern
Date: 03/09/1999 02:10:03
Hi !

(Huh ! I found Ross's message a little rude about Greg's work and mine).

As Greg said, I just want to use his work instead of rewriting all the
stuff. But I already wrote some code before that, so I could write my own
driver , in a different way. Morally, I will give him credits in the source
code, even if I don't use his code.

But the question is still here. We should find a solution to not exclude
Greg code, past present and future (I say Greg, but maybe someone else have
the same reticence). Maybe a modification of the standard NetBSD copyright
notice will be acceptable by both side ? I'm not a jurist, and copyrights
are differents on this side of the sea.

Thanks.

PS: I have changed the title 'cause it was awfull. I should read my messages
2 times before sending them. Sorry.
--
Eric Delcamp......................NetBSD i386 & Amiga, BeOS, Windows NT
Merignac..........................Distributed.net : < 7900th (15/02/99)
France............................Magic the Gathering player

-----Message d'origine-----
De : Jason Thorpe <thorpej@nas.nasa.gov>
 : Ross Harvey <ross@ghs.com>
Cc : e.delcamp@wanadoo.fr <e.delcamp@wanadoo.fr>; tech-kern@netbsd.org
<tech-kern@netbsd.org>
Date : mardi 9 mars 1999 00:26
Objet : Re: Last chance: Copyrights is OK ?


>On Mon, 8 Mar 1999 14:39:45 -0800 (PST)
> Ross Harvey <ross@ghs.com> wrote:
>
> > The LM78 is a simple chip with the usual excellent NSC documentation,
> > downloadable(*) in pdf form by anyone.  Rather than accept a problematic
> > license, what we need is to find any random kernel weenie with one of
these
> > devices, and get you a new driver without copyright problems.  Any
kernel
> > hacker can write this driver for you, it requires no particular
expertise
> > other than general driver capability.
>
>I agree.  My vote here would be:
>
> Either it is assigned to TNF, or we re-implement the functionality.