From owner-freebsd-current@FreeBSD.ORG Wed May 28 16:48:04 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 DBBF637B401 for ; Wed, 28 May 2003 16:48:04 -0700 (PDT) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id C007743F3F for ; Wed, 28 May 2003 16:48:02 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.8) with ESMTP id h4SNligD003064; Thu, 29 May 2003 09:17:45 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "M. Warner Losh" Date: Thu, 29 May 2003 09:17:44 +0930 User-Agent: KMail/1.5 References: <200305281147.53271.doconnor@gsoft.com.au> <200305281524.10145.doconnor@gsoft.com.au> <20030528.031403.32720860.imp@bsdimp.com> In-Reply-To: <20030528.031403.32720860.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305290917.44200.doconnor@gsoft.com.au> X-Spam-Score: -1.5 () CARRIAGE_RETURNS,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) 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 23:48:05 -0000 On Wed, 28 May 2003 18:44, M. Warner Losh wrote: > : 1) If the port is updated between builds you end up with two version of > : the port installed. > > True. That's a weakness in the ports system, which is why we have > portupgrade. However, I didn't want to require portupgrade for > something so 'simple'. To a degree, but IMHO it isn't correct - I don't want to update the version of the port I am using without good reason. ie it should just recompile the code for the port you've already installed which is usually sufficient to get things working again. > : 2) You can't control where the module gets put - arguably this isn't a > : calamity, but I think it makes more sense for the modules to end up in > : /boot/modules, or some analog to it that is in $PREFIX. > > It should go in /boot/kernel, and not into $PREFIX, but that's a > philisophical problem I have with ports. ALL modules should be in /, > imho, since you don't know if the module is required to mount /. Yes, I agree. > : 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.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5