From owner-freebsd-current@FreeBSD.ORG Tue May 27 21:03:56 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 C56CF37B401 for ; Tue, 27 May 2003 21:03:56 -0700 (PDT) Received: from basement.kutulu.org (pcp03610121pcs.longhl01.md.comcast.net [68.49.239.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB74843F75 for ; Tue, 27 May 2003 21:03:53 -0700 (PDT) (envelope-from kutulu@kutulu.org) Received: by basement.kutulu.org (Postfix, from userid 1001) id CEDB9A947; Wed, 28 May 2003 00:04:06 -0400 (EDT) Date: Wed, 28 May 2003 00:04:06 -0400 From: Michael Edenfield To: Scott Long Message-ID: <20030528040406.GA46917@basement.kutulu.org> Mail-Followup-To: Scott Long , Q , freebsd-current@freebsd.org References: <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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <3ED4315F.8080709@btc.adaptec.com> User-Agent: Mutt/1.4.1i X-Mailer: Mutt http://www.mutt.org/ X-Accept-Language: en X-PGP-Key: http://www.kutulu.org/pgp/kutulu.asc X-PGP-Fingerprint: 1CE0 3C31 7013 D529 406D 37DC 09CC CD84 A46C 878F cc: Q 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 04:03:57 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Scott Long [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. >=20 > 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=20 /boot/kernel instead of /usr/local/wherever/it/goes/now? I=20 understand why most aren't put there now, due to the seperation of=20 base system from ports etc. But I would the benefits of violating=20 that principle outweigh the detriments: each time you reinstall your=20 kernel, /boot/kernel is moved out of the way... taking all the=20 outdated modules with it. Your port modules would fail to load, not=20 being in the right place, but that's far better than a panic. --Mike --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+1DU0CczNhKRsh48RAoWvAKCr2JNBiy+7K8z1S9tuPPBfQuLy0wCeL4Go RpAfA9NdhBZ2IqAvCtUWq+E= =wMU/ -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--