summaryrefslogtreecommitdiff
path: root/emulators/vmware3
diff options
context:
space:
mode:
authorjdolecek <jdolecek@pkgsrc.org>2004-10-16 15:20:01 +0000
committerjdolecek <jdolecek@pkgsrc.org>2004-10-16 15:20:01 +0000
commitaa387320d474fe3750292cc6f33bbb3a80614d27 (patch)
treed95c267f27c8d41f04cdaaf4834864976ba0fef4 /emulators/vmware3
parent778372c647892a2a665a17f7219c5b0d357a5858 (diff)
downloadpkgsrc-aa387320d474fe3750292cc6f33bbb3a80614d27.tar.gz
move the message from (generic) MESSAGE to MESSAGE.NetBSD, since it's
NetBSD-only problem also clarify what was the cause the problem and which version of NetBSD fixed it
Diffstat (limited to 'emulators/vmware3')
-rw-r--r--emulators/vmware3/MESSAGE11
-rw-r--r--emulators/vmware3/MESSAGE.NetBSD11
2 files changed, 11 insertions, 11 deletions
diff --git a/emulators/vmware3/MESSAGE b/emulators/vmware3/MESSAGE
deleted file mode 100644
index 10e32bc201c..00000000000
--- a/emulators/vmware3/MESSAGE
+++ /dev/null
@@ -1,11 +0,0 @@
-===========================================================================
-$NetBSD: MESSAGE,v 1.3 2003/03/30 04:21:25 grant Exp $
-
-Since VMware 3.x, there is a problem which might be related to shared
-memory under Linux emulation, giving as a result black screen.
-Unfortunately, it's extremely hard to track down what's going on and this
-is as yet unresolved.
-
-If you experience this problem, setting your DISPLAY environment variable
-to "localhost:0" should help.
-===========================================================================
diff --git a/emulators/vmware3/MESSAGE.NetBSD b/emulators/vmware3/MESSAGE.NetBSD
new file mode 100644
index 00000000000..348571feda5
--- /dev/null
+++ b/emulators/vmware3/MESSAGE.NetBSD
@@ -0,0 +1,11 @@
+===========================================================================
+$NetBSD: MESSAGE.NetBSD,v 1.1 2004/10/16 15:20:01 jdolecek Exp $
+
+NetBSD had problem with emulation of Linux SVID shared memory handling,
+which caused black screen in VMware 3.x when the guest OS switched
+to graphics mode. The problem has been fixed in NetBSD 2.99.9 and
+2.0RC3.
+
+If you experience this problem, setting your DISPLAY environment variable
+to "localhost:0" should help.
+===========================================================================