Date: Wed, 28 May 2003 00:04:06 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: Scott Long <scott_long@btc.adaptec.com> Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <20030528040406.GA46917@basement.kutulu.org> In-Reply-To: <3ED4315F.8080709@btc.adaptec.com> References: <C90CF9CA-9040-11D7-941E-0003937E39E0@mac.com> <200305281147.53271.doconnor@gsoft.com.au> <1054090968.1429.10.camel@boxster> <3ED4294B.4040108@btc.adaptec.com> <1054092793.1429.39.camel@boxster> <3ED4315F.8080709@btc.adaptec.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] * Scott Long <scott_long@btc.adaptec.com> [030527 23:51]: > >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. Wouldn't it be sufficient to simply install the port modules into /boot/kernel instead of /usr/local/wherever/it/goes/now? I understand why most aren't put there now, due to the seperation of base system from ports etc. But I would the benefits of violating that principle outweigh the detriments: each time you reinstall your kernel, /boot/kernel is moved out of the way... taking all the outdated modules with it. Your port modules would fail to load, not being in the right place, but that's far better than a panic. --Mike [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+1DU0CczNhKRsh48RAoWvAKCr2JNBiy+7K8z1S9tuPPBfQuLy0wCeL4Go RpAfA9NdhBZ2IqAvCtUWq+E= =wMU/ -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030528040406.GA46917>