Date: Wed, 28 May 2003 13:50:27 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Scott Long <scott_long@btc.adaptec.com>, Q <q_dolan@yahoo.com.au> Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <200305281350.27953.doconnor@gsoft.com.au> In-Reply-To: <3ED4315F.8080709@btc.adaptec.com> References: <C90CF9CA-9040-11D7-941E-0003937E39E0@mac.com> <1054092793.1429.39.camel@boxster> <3ED4315F.8080709@btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 May 2003 13:17, Scott Long wrote: > > I am thinking of ports like rtc, ltmdm or Vmware here.. where it is not > > uncommon that they require reinstalling after an upgrade. I have > > experienced kernel panics on several occasions from out of date vmware > > kernel modules. > > I'm really of the opinion that these ports should either live in the > sys/ tree, or that magic should be devised to make sure that they are > built along with the rest of the modules. Agreed :) I don't think it makes sense committing them into the sys tree, as it bloats everyones system and has potential licensing problems. Maybe the kernel build stuff can look in /usr/local/src/sys/modules for things to build or something.. -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305281350.27953.doconnor>