On Tue, Nov 11, 2008 at 3:12 PM, Allistar <[EMAIL PROTECTED]> wrote: > Kevin O'Gorman wrote: > >> On Tue, Nov 11, 2008 at 12:43 AM, Neil Bothwick <[EMAIL PROTECTED]> >> wrote: >>> On Mon, 10 Nov 2008 19:24:15 -0800, Kevin O'Gorman wrote: >>> >>>> I've re-emerge vmware-modules, re-run ...vmware-config.pl, and prayed. >>>> I still cannot do >>>> /etc/init.d/vmware start >>>> because this one part fails: Virutal machine Monitor >>>> and trying "vmware&" says I need to run the config script (again). >>>> >>>> I'm getting nowhere and I really do want to run that VM again. >>>> >>> >>> Have you updated your kernel? VMware Workstation gives me problems like >>> this with each new kernel, which is why I'm still running 2.6.26 on my >>> desktop. >>> >> >> I'm running 2.6.25-r8. I probably have updated since the last time I >> ran VMware. >> But I thought the above steps took care of that. I guess not. >> >> So what do I do now? > > From what I've experienced, the order you emerge vmware-workstation and > vmware-modules is important. When getting the error you mention, a simple > re-emerge of vmware-modules did the job.
This did not help. I tried downloading VMWare-workstation, but the emerge fails on fetch restrictions, and the message points to a file on a server that denies it has such a file. The workstation bundle runs an installer that wants a runlevel directory, but rejects the /etc/runlevels directory and subdirectories. I'm guessing it wants something more like SYSV. -- Kevin O'Gorman, PhD
