From owner-freebsd-current Fri Nov 7 00:40:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA18880 for current-outgoing; Fri, 7 Nov 1997 00:40:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA18873; Fri, 7 Nov 1997 00:40:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id JAA01608; Fri, 7 Nov 1997 09:39:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" cc: dyson@FreeBSD.ORG, 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:54:35 PST." <15223.878889275@time.cdrom.com> Date: Fri, 07 Nov 1997 09:39:09 +0100 Message-ID: <1606.878891949@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <15223.878889275@time.cdrom.com>, "Jordan K. Hubbard" writes: >> 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. We already have that, we just don't use it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."