Re: vmnet.ko missing - but it's there! - vmware and crashes

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