From owner-freebsd-current  Thu Nov  6 23:54:41 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA16859
          for current-outgoing; Thu, 6 Nov 1997 23:54:41 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA16854;
          Thu, 6 Nov 1997 23:54:35 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id XAA15227; Thu, 6 Nov 1997 23:54:35 -0800 (PST)
To: dyson@FreeBSD.ORG
cc: scottm@cs.ucla.edu (Scott Michel), freebsd-current@FreeBSD.ORG
Subject: Re: Latest kernel: panics with NFS LKM 
In-reply-to: Your message of "Thu, 06 Nov 1997 23:59:55 EST."
             <199711070459.XAA00517@dyson.iquest.net> 
Date: Thu, 06 Nov 1997 23:54:35 -0800
Message-ID: <15223.878889275@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Remember to rebuild all of the LKM's.  We should probably come up with
> a published list of things (worst case) that need to be rebuit when
> upgrading a kernel.  People can usually get by with simply

Either that or we need to simply add versioning to the LKM mechanism.
With Peter's recent changes to config(8), that dependency is a bit
more properly handled now and I guess LKMs are the only hold-out.

						Jordan