From owner-freebsd-hackers Wed May 8 15:53:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA02407 for hackers-outgoing; Wed, 8 May 1996 15:53:15 -0700 (PDT) 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 PAA02401 for ; Wed, 8 May 1996 15:53:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA26988; Wed, 8 May 1996 15:43:12 -0700 From: Terry Lambert Message-Id: <199605082243.PAA26988@phaeton.artisoft.com> Subject: Re: Copyright question To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 8 May 1996 15:43:12 -0700 (MST) Cc: eischen@vigrid.com, jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <9605082158.AA09404@pcnet1.pcnet.com> from "Daniel Eischen" at May 8, 96 05:58:27 pm 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 X-Loop: FreeBSD.org Precedence: bulk > I'll try to see if I can get rid of clause 4, but I don't think > they're going to let it go without some sort of clause. Is there > anything we can do? Add a comment in LINT saying it's restricted > by copyright? Or point to a file from within LINT that will list > the restricted driver(s)? As long as the user sees the copyright > restriction before he rebuilds the kernel with the driver, right? If devfs and LKM were fully integrated, you could distribute it as a binary loadable, no source required. This assumes that it's not ever going to be used to run the console or other boot-critical uses (ie: somewhat limited utility). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.