From owner-freebsd-hackers Mon Dec 18 12:34:20 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA17896 for hackers-outgoing; Mon, 18 Dec 1995 12:34:20 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA17890 for ; Mon, 18 Dec 1995 12:34:16 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA12258; Mon, 18 Dec 1995 13:28:13 -0700 From: Terry Lambert Message-Id: <199512182028.NAA12258@phaeton.artisoft.com> Subject: Re: rusers(3) & rnusers(3) To: jau@jau.csc.fi (Jukka Ukkonen) Date: Mon, 18 Dec 1995 13:28:13 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, hackers@FreeBSD.org In-Reply-To: <199512180938.LAA09745@jau.csc.fi> from "Jukka Ukkonen" at Dec 18, 95 11:38:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > Notice also that I sent the code to others to test and review. > The actual licensing terms can be adjusted to a more suitable > and more formal representation later if necessary (maybe to BSD > or GNU style) if you think you wish to include the code in the > FreeBSD distribution. (The same goes naturally for NetBSD or > Linux or whatever freely available UNIX style OS, which you can > grab from the net.) > > My note simply meant that you can distribute the code without > limitation to anyone who is interested, but _for the moment_ > I am still the owner of the rights to it, whether there is any > "intellectual" property contained in it or not. I don't have problems with this. However, if the code is integrated into the main line kernel or libraries, this would count as a significant restriction. Thre is a reason that BSD does not support every driver that Linux supports, and Licensing is it. If it's your intent to put it under BSD-style license for the actual release, then fine. My intent was only to prevent integration until such time. Jordan seemed a bit gung-ho to include it, and I saw no real problems with the code as presented. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.