public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: vmware fails: Virtual Machine Monitor does not start
Date: Tue, 11 Nov 2008 18:03:55 -0800	[thread overview]
Message-ID: <9acccfe50811111803n78d2ce04j76833eb764e30993@mail.gmail.com> (raw)
In-Reply-To: <gfd3eb$7c4$1@ger.gmane.org>

On Tue, Nov 11, 2008 at 3:12 PM, Allistar <allistar.m@gmail.com> wrote:
> Kevin O'Gorman wrote:
>
>> On Tue, Nov 11, 2008 at 12:43 AM, Neil Bothwick <neil@digimed.co.uk>
>> 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



  reply	other threads:[~2008-11-12  2:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  3:24 [gentoo-user] vmware fails: Virtual Machine Monitor does not start Kevin O'Gorman
2008-11-11  8:43 ` Neil Bothwick
2008-11-11 21:53   ` [gentoo-user] " Allistar
2008-11-11 22:33     ` Neil Bothwick
2008-11-11 22:53   ` [gentoo-user] " Kevin O'Gorman
2008-11-11 22:57     ` Kevin O'Gorman
2008-11-11 23:01       ` William Kenworthy
2008-11-11 23:37       ` Neil Bothwick
2008-11-12  0:20         ` Kevin O'Gorman
2008-11-12  0:31           ` William Kenworthy
2008-11-12  1:48           ` Neil Bothwick
2008-11-12  2:19           ` Kevin O'Gorman
2008-11-11 23:04     ` Andrey Falko
2008-11-12  2:30       ` Kevin O'Gorman
2008-11-11 23:12     ` [gentoo-user] " Allistar
2008-11-12  2:03       ` Kevin O'Gorman [this message]
2008-11-12  2:12         ` Neil Bothwick
2008-11-12  2:34         ` Noven
2008-11-12  3:19           ` Kevin O'Gorman
2008-11-12  3:25             ` Kevin O'Gorman
  -- strict thread matches above, loose matches on Subject: below --
2008-11-12  4:16 Noven
2008-11-13  5:02 ` Kevin O'Gorman
2008-11-13  7:03   ` Iain Buchanan
2008-11-13  7:37   ` Noven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9acccfe50811111803n78d2ce04j76833eb764e30993@mail.gmail.com \
    --to=kogorman@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox