Date: Thu, 06 Mar 2003 09:42:17 -0600 From: Kirk Strauser <kirk@strauser.com> To: freebsd-hackers@freebsd.org Subject: Re: Smarter kernel modules? Message-ID: <87n0k8cxie.fsf@strauser.com> In-Reply-To: <20030306070940.GA93350@cirb503493.alcatel.com.au> (Peter Jeremy's message of "Thu, 6 Mar 2003 18:09:40 %2B1100") References: <20030306030852.GA1158@edgemaster.zombie.org> <878yvtdpp0.fsf@strauser.com> <20030306070940.GA93350@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Transfer-Encoding: quoted-printable At 2003-03-06T07:09:40Z, Peter Jeremy <peterjeremy@optushome.com.au> writes: > 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. Is the new system documented anywhere? I had assumed that it was analogous to Linux's (Debian's, at least) system. I have several entries under /lib/modules: $ ls 2.2.20 2.4.17-k7 2.4.18-k7 2.4.19-k7 Whenever I boot one of the respective kernels, it looks for its modules in /lib/modules/$VERSION so that there's no real possibility for catastrophic interaction. =2D-=20 Kirk Strauser In Googlis non est, ergo non est. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+Z2xZ5sRg+Y0CpvERAqhvAJkB2rnBTrWEAj/qvtCrvoVyGV5qSACcDjWm A5WsaZ+/0oJn4Q5kkBPs14g= =Sk5s -----END PGP SIGNATURE----- --=-=-=-- 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?87n0k8cxie.fsf>