Date: Thu, 6 Mar 2003 18:09:40 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Smarter kernel modules? Message-ID: <20030306070940.GA93350@cirb503493.alcatel.com.au> In-Reply-To: <878yvtdpp0.fsf@strauser.com> References: <20030306030852.GA1158@edgemaster.zombie.org> <878yvtdpp0.fsf@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 05, 2003 at 11:33:31PM -0600, Kirk Strauser wrote: >At 2003-03-06T03:08:52Z, Sean Kelly <smkelly@zombie.org> writes: > >> Has anyone ever considered embedding some sort of identifier in kernel >> modules to keep them from being loaded with the wrong kernel? > >Unless I'm mistaken, 5.0 supports having multiple kernels installed, each >with their own modules directories, under /boot. Yes, but this doesn't resolve the versioning issue. 1) If you update any of those kernels, the updated kernel and updated modules will be written into /boot/FOO/ as appropriate. BUT old modules that weren't rebuilt (eg 3rd party modules) will remain in /boot/FOO/. If the new kernel happened to change an API, you're likely to get a panic when you load the old module. 2) -CURRENT apparently looks in /modules/ as well as /boot/kernel/ - and any module found in the former is probably 4.x which will cause things to fail spectacularly. Versioning is the only way to solve both these problems. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030306070940.GA93350>