![](https://seccdn.libravatar.org/avatar/915019de619bbec0b54555e3c7a46107.jpg?s=120&d=mm&r=g)
On Tuesday 19 February 2008 10:49:12 Carlos E. R. wrote:
The Tuesday 2008-02-19 at 10:39 +0800, Jonathan Ervine wrote:
No, it is that script that has not been mantained in ages.
vmware-config.pl? Oh.
I find it rather bizarre that I have to run it every time I upgrade my kernel. i notice this isn't the issue with Virtual Box.
Ummm - why should it be bizarre to run a script that compiles kernel
Hold on, it seems you didn't see my email in which I said the problem script is not 'vmware-config.pl' but 'vmware-mount.pl'
Apologies - I first checked on my test system, running VMware server 2 beta. You'll no doubt be delighted to know that the perl script has been replaced with a vmware-mount binary file there.
The copyright notice on a specific script/source code is no indication as to when it has last been modified/changed. Shock: the /etc/inittab file has copyright 1996-2002 written in it. The vmware-config.pl file has copyright 1998-2007 written. Anyone want to make a wild guess as to when the scripts were originally written and the last update made?
No, the problem is not simply the copyright notice. The problem is that the script complains that the kernel is newer than 2.4 and that is known to be problematic. It's a kernel too new for the script.
The script warns that it has been reported that it can be problematic in some cases. Still seems to mount the disk images just fine though. I can't help but feeling you're making a crisis out of a minor drama here. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org