From owner-freebsd-current@FreeBSD.ORG  Thu Jul 22 19:32:23 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 4A0F616A4CE; Thu, 22 Jul 2004 19:32:23 +0000 (GMT)
Received: from mail024.syd.optusnet.com.au (mail024.syd.optusnet.com.au
	[211.29.132.242])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2F5A243D1F; Thu, 22 Jul 2004 19:32:22 +0000 (GMT)
	(envelope-from PeterJeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au
	(c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229])
	i6MJWG810936;	Fri, 23 Jul 2004 05:32:16 +1000
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au
	[127.0.0.1])i6MJWDVd010313;	Fri, 23 Jul 2004 05:32:15 +1000 (EST)
	(envelope-from pjeremy@cirb503493.alcatel.com.au)
Received: (from pjeremy@localhost)i6MJWDYU010312;
	Fri, 23 Jul 2004 05:32:13 +1000 (EST)	(envelope-from pjeremy)
Date: Fri, 23 Jul 2004 05:32:13 +1000
From: Peter Jeremy <PeterJeremy@optushome.com.au>
To: Mark Santcroos <marks@ripe.net>
Message-ID: <20040722193213.GJ3001@cirb503493.alcatel.com.au>
References: <40FE8F81.7040409@freebsd.org>
	<Pine.NEB.3.96L.1040721115940.56342A-100000@fledge.watson.org>
	<20040722130601.GA2751@laptop.6bone.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040722130601.GA2751@laptop.6bone.nl>
User-Agent: Mutt/1.4.2i
cc: "freebsd -current@" <freebsd-current@freebsd.org>
cc: Robert Watson <rwatson@freebsd.org>
Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jul 2004 19:32:23 -0000

On Thu, 2004-Jul-22 15:06:01 +0200, Mark Santcroos wrote:
>IMHO the most important point to reach is that it can't happen anymore that
>we load an out-of-sync vmware module at boot time and panic. It should either
>be correctly rebuild or not installed at all (and removed).

The nicest way to do this would be to add versioning to the kld interface
but this isn't practical (there was a thread about this some time ago).
There are two other fairly easy approaches to this:
1) Change installkernel so that it does
	mv /boot/kernel /boot/kernel.old
   instead of something like
	cp -p /boot/kernel/* /boot/kernel.old
2) Add a check for old files in /boot/kernel at the end of installkernel
   and generate a banner message "The following modules are out of date..."

-- 
Peter Jeremy