Not sure where the failure is, but the init script that we provide in /etc/init.d/ fails to load on either of my boxes - but running /etc/vmware/init.d/vmware start works without a hitch. Reproducible: Always Steps to Reproduce: 1. 2. 3.
example output of the failure *might* be helpful :P
Maybe a emerge info, the package version, and a kernel version, too, please...
There is no example of output spanks ;) Example output is the init script saying it fails to load (but loads the modules) then dieing. Example output of it working is the original script running and saying "done" and then vmware actually working. Wolf - will have to get you the emerge info on Monday (this box is at work). It's a 2.4.22 gentoo sources, vmware is the current stable - 4.0.5.6030, and its an intel p4. When I get you that output, granting that I don't need to get into vmware asap (it's my access to the office lan), i'll see if i can get the gentoo init script to be more verbose. It happens during the call/parsing of vmware-prettify, but I didn't have a chance to isolate it more than that.
Well, I can't seem to reproduce the problem at all. Is it possible that we made a change to the init script and you didn't update it when updating the rest of the package? I have tried using 2.4.x and 2.6.x on x86 (athlon-mp, p4, p3) and amd64 and am not having any troubles with the init scripts.
This seems to have gone away with the last update of vmware. Don't want to step on toes (ok, not sure who gets the "credit" if i close the bug myself). After this week's emerge -u it went away. Weird. Really sorry for the bother, -mike
No problem, man... closed... =]
