From owner-freebsd-current@FreeBSD.ORG Wed May 28 07:37:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A88537B401 for ; Wed, 28 May 2003 07:37:53 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9547D43F93 for ; Wed, 28 May 2003 07:37:52 -0700 (PDT) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h4SEXBZ06410; Wed, 28 May 2003 07:33:11 -0700 Received: from btc.adaptec.com (hollin.btc.adaptec.com [10.100.253.56]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id HAA23922; Wed, 28 May 2003 07:37:36 -0700 (PDT) Message-ID: <3ED4C911.2000007@btc.adaptec.com> Date: Wed, 28 May 2003 08:34:57 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <200305281350.27953.doconnor@gsoft.com.au> <200305281447.02322.doconnor@gsoft.com.au> <20030528.030900.55833611.imp@bsdimp.com> <200305281840.46645.doconnor@gsoft.com.au> <20030528142837.GA30174@troutmask.apl.washington.edu> In-Reply-To: <20030528142837.GA30174@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: q_dolan@yahoo.com.au cc: "M. Warner Losh" cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 14:37:53 -0000 Steve Kargl wrote: > On Wed, May 28, 2003 at 06:40:46PM +0930, Daniel O'Connor wrote: > >>On Wed, 28 May 2003 18:39, M. Warner Losh wrote: >> >>>: > : Maybe the kernel build stuff can look in /usr/local/src/sys/modules >>>: > : for things to build or something.. >>>: > >>>: > YUCK! >>>: >>>: *WHY?* >>>: >>>: I have asked this before BTW, and I haven't been told why it sucks. >>> >>>Because there are other, more elegant ways of dealing with these >>>things. I don't like /usr/local/src anything, which was the main >>>complaint. >> >>If there are more elegant solutions I would like to know what they are. >> >>I agree it isn't a great solution, but I can't see what is better. >> > > > For GPL modules, put them in src/sys/gnu. If you don't > want bloat, then use cvsup and a refuse file to not > retrieve the sys/gnu. See the discussion that occurred > many years ago when maestro3 support was committed to > the tree. > > For non-viral licensed code, put it in its proper > place in the sys/ hierarchy. Then use a WANT_XXX=yes > knob in the /etc/make.conf to cause XXX to be built. > It should be noted that the maestro3 case only involved the firmware being GPL, not the whole driver (I and the other author had explicit permission to license the kernel portion as BSDL). I still wonder about the validity of GPLing hexidecimal digits that represent binary machine code..... Scott