From owner-freebsd-current@FreeBSD.ORG Wed May 28 16:54:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id E4F5D37B401; Wed, 28 May 2003 16:54:07 -0700 (PDT) Date: Wed, 28 May 2003 18:54:07 -0500 From: Juli Mallett To: Daniel O'Connor Message-ID: <20030528185407.A97781@FreeBSD.org> References: <200305281147.53271.doconnor@gsoft.com.au> <200305281524.10145.doconnor@gsoft.com.au> <20030528.031403.32720860.imp@bsdimp.com> <200305290917.44200.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200305290917.44200.doconnor@gsoft.com.au>; from doconnor@gsoft.com.au on Thu, May 29, 2003 at 09:17:44AM +0930 X-Title: Code Maven X-Towel: Yes X-Negacore: Yes X-Authentication-Warning: localhost: juli pwned teh intarweb cc: freebsd-current@freebsd.org cc: "M. Warner Losh" 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 23:54:08 -0000 * Daniel O'Connor [ Date: 2003-05-28 ] [ w.r.t. Re: policy on GPL'd drivers? ] > > : I guess the problem with mandating somewhere in $PREFIX is that the > > : loader can't load it, so that's no good. I guess the only choice left is > > : /boot/modules. > > > > /boot/kernel > > > > : Any comments? > > > > Well, the patch was mostly a strawman to promote discussions about the > > issues. > > Fair enough. > > I think the port should install the source for the module in $PREFIX somewhere > (well known) and the module should live in /boot/kernel. > > When things need rebuilding it uses the installed source to do so.. Jumping in a bit late as I thought someone would point this out, but I thought that 3rd-party modules would live in /boot/modules? Also, as for them being tied to kernel configs at minimum, definitely, and I'd say that maybe /boot/modules should have e.g. foobar-IDENT.ko and a symlink to it from /boot/kernel.IDENT/foobar.ko or something, where IDENT is the kernel IDENT, that way multiple copies of a given 3rd-party module could exist, and probably we'd want to do something similar to the .old shuffling we do with kernels, anyway. Just a thought. Just putting them *with* each kernel does seeem a lot more direct, for sure, but I'd feel less gross adding a new symlink than copying one from an existing directory, which could be crudded up with $DEITY knows what. Thanx, juli. -- juli mallett. email: jmallett@freebsd.org; efnet: juli;