From owner-freebsd-current@FreeBSD.ORG Tue May 27 20:02:55 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 047FC37B401 for ; Tue, 27 May 2003 20:02:55 -0700 (PDT) Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 83BC643F75 for ; Tue, 27 May 2003 20:02:54 -0700 (PDT) (envelope-from q_dolan@yahoo.com.au) Received: from vdub.onthenet.net (HELO ?172.22.1.10?) (q?dolan@203.10.89.16 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 May 2003 03:02:53 -0000 From: Q To: Daniel O'Connor In-Reply-To: <200305281147.53271.doconnor@gsoft.com.au> References: <200305281147.53271.doconnor@gsoft.com.au> Content-Type: text/plain Organization: Message-Id: <1054090968.1429.10.camel@boxster> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 28 May 2003 13:02:49 +1000 Content-Transfer-Encoding: 7bit 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 03:02:55 -0000 I have been burnt by this in the past also. I think that it would be useful if you could allow kernel modules to be bound to a particular kernel "version/date/whatever", and have external modules refuse to load and/or complain if the kernel is upgraded. This should prevent unnecessary kernel panics when you upgrade. The Linux kernel has been doing this for years. Seeya...Q On Wed, 2003-05-28 at 12:17, Daniel O'Connor wrote: > On Tue, 27 May 2003 22:13, David Leimbach wrote: > > > However the idea is that all GPL infected stuff be isolated, allowing a > > > fully working kernel without GPL stuff in there. > > > > Sounds like a "kernel module" is the way to go then. Perhaps it could > > exist in the ports tree instead of the mainline kernel sources :). I > > know > > I'd be happy with that... the problem is hosting the driver since I am > > sure > > "patching" it won't be enough to map the linux innards to freebsd's. > > There are already a number of kernel modules in the ports tree (eg nvidia > drivers, ltmdm modem driver, aureal sound driver, etc). > > The only downside is that there are no hooks into the build process so you > have to be VERY careful when you update your kernel, or you get panics :( > > (I found this recently, some change broke all of my 3rd party modules and > caused panics when I tried to load them). > > I would really like some way of getting external modules rebuilt at the same > time as buildkernel and friends, otherwise you have to remember to rebuild > the affected ports, and it is a pain in the ass. -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan - q@OntheNet.com.au __ __/ / / __/ / / / __ / _/ / / Gold Coast, QLD, Australia __/ __/ __/ ____/ / - / Ph: +61 419 729 806 _______ / _\