From owner-freebsd-current@FreeBSD.ORG  Thu Jul 22 20:03:05 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 4C78E16A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 22 Jul 2004 20:03:05 +0000 (GMT)
Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.246])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2CFE943D41
	for <freebsd-current@freebsd.org>;
	Thu, 22 Jul 2004 20:03:05 +0000 (GMT)
	(envelope-from swhetzel@gmail.com)
Received: by mproxy.gmail.com with SMTP id u22so21280cwc
	for <freebsd-current@freebsd.org>;
	Thu, 22 Jul 2004 13:03:01 -0700 (PDT)
Received: by 10.11.100.20 with SMTP id x20mr49034cwb;
        Thu, 22 Jul 2004 13:03:01 -0700 (PDT)
Message-ID: <790a9fff040722130326edaed7@mail.gmail.com>
Date: Thu, 22 Jul 2004 15:03:01 -0500
From: Scot Hetzel <swhetzel@gmail.com>
To: Peter Jeremy <peterjeremy@optushome.com.au>
In-Reply-To: <20040722193213.GJ3001@cirb503493.alcatel.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <40FE8F81.7040409@freebsd.org>
	<Pine.NEB.3.96L.1040721115940.56342A-100000@fledge.watson.org>
	<20040722193213.GJ3001@cirb503493.alcatel.com.au>
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 20:03:05 -0000

On Fri, 23 Jul 2004 05:32:13 +1000, Peter Jeremy
<peterjeremy@optushome.com.au> wrote:
> 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..."
> 
Except that won't work for modules installed by ports.  These modules
are not installed into a standard location.  Some are installed into
${PREFIX}/modules, ${PREFIX}/lib/<module name>, /modules,
/boot/modules.  What should happen is that all modules installed by
ports/packages should install into a common location.  Then the
installkernel target could show out of date port/package modules.

Scot