From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: VMware problems
Date: Sat, 31 Mar 2007 23:44:25 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.03.31.23.44.25@cox.net> (raw)
In-Reply-To: 460E1C6F.1030503@yahoo.de
Stefan Ruester <stefan_ruester@yahoo.de> posted 460E1C6F.1030503@yahoo.de,
excerpted below, on Sat, 31 Mar 2007 10:31:43 +0200:
> So the system hangs at a read from "VmPerl.so". A second trace stopped
> at exactly the same position which makes me think there around might be
> the problem.
That would suggest running revdep-rebuild. Have you run it lately?
(It's possible you mentioned doing so at the top of the thread, but I'm
headed to work and don't have time to check at the moment.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-03-31 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 18:17 [gentoo-amd64] VMware problems Stefan Ruester
2007-03-30 19:16 ` Brett Johnson
2007-03-31 8:31 ` Stefan Ruester
2007-03-31 23:44 ` Duncan [this message]
2007-04-04 10:33 ` [gentoo-amd64] " Stefan Ruester
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=pan.2007.03.31.23.44.25@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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