Problems starting vmware server and using vmware-config.pl after switching to baselaout 2. The same scripts work with baselayout 1.x without any trouble. Reproducible: Always Steps to Reproduce: 1. # /etc.init.d/wmware start 2. # vmware-config.pl 3. Actual Results: The first command gives the following trace: * Caching service dependencies ... FATAL: Module k8tempmodprobe not found. /etc/init.d/vmware: line 67: `vmware-prettify': not a valid identifier [ ok ] /etc/init.d/vmware: line 67: `vmware-prettify': not a valid identifier * ERROR: vmware failed to start The second one: Making sure services for VMware Server are stopped. * WARNING: vmware is already stopped Unable to stop services for VMware Server Execution aborted. Expected Results: The first command should have started the vmware service that is the modules should have been loaded and the server should be listening on port 902. The second command should invoke the vmware configuration script. vmware-config.pl is expected to be invoked after a new installation of the vmware server or when the configuration needs to be updated e.g. when a new kernel has been installed. /etc/init.d/vmware start seems to fail because baselayout 2 seems to be more strict about identifiers than baselayout 1.x. The problem is the following function name: vmware-prettify(). Changing that to vmware_prettify() resolves the problem. I am not sure why the vmware-config.pl fails but a quick workaround is to invoke it with the -skipstopstart option (of course one has to be sure that the modules are unloaded and the vmware server is not running while doing that). I am using vmware-server only but I suspect that all other vmware products that is workstation and player may be affected.
vmware init scripts need to use POSIX compliant function names. Basically change the - to _
This has already been updated in the overlay. The changes will get pushed out to the main tree in the next week or so, which should happen before the new baselayout gets unmasked...
Just committed the fixed versions to the tree, so they should hit the mirrors in a couple of hours. I'm marking this as fixed, please feel free to reopen this if you still experience problems after re-emerging any of the vmware packages... 5:)
