linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: erich@uruk.org
To: linux-kernel@vger.kernel.org
Subject: Small fix for VMWare 3.2 (3.x?) on Redhat 9 (any 2.4.20+ kernel?)
Date: Fri, 11 Apr 2003 03:34:45 -0700	[thread overview]
Message-ID: <E193vrp-0006P4-00@trillium-hollow.org> (raw)


FYI...

I'm running Redhat 9, and to get my copy of VMWare 3.2 working with it,
I had to make a one-line fix to a source file inside the "vmnet.tar" file
for building the vmnet module.

With the fix, VMWare's scripts throw off a lot of what seem to be
irrelevant error messages while configuring, but it runs flawlessly
once the "vmware-config.pl" script completes.

In the default installation, the source files for the vmnet module are in:

   /usr/lib/vmware/modules/source/vmnet.tar

Here's the patch:
------------------------------------------------------------------------
diff -ruN vmnet-only.orig/driver.c vmnet-only/driver.c
--- vmnet-only.orig/driver.c    2002-09-09 20:22:41.000000000 -0700
+++ vmnet-only/driver.c 2003-04-10 18:51:22.000000000 -0700
@@ -1485,7 +1485,7 @@
     
    len += sprintf(buf+len, "pids ");
  
-   for_each_task(p) {
+   for_each_process(p) {
       if (VNetProcessOwnsPort(p, port)) {
          len += sprintf(buf+len, "%d", p->pid);
          if (seen) {
------------------------------------------------------------------------

--
    Erich Stefan Boleyn     <erich@uruk.org>     http://www.uruk.org/
"Reality is truly stranger than fiction; Probably why fiction is so popular"



             reply	other threads:[~2003-04-11 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 10:34 erich [this message]
2003-04-16  4:42 ` Small fix for VMWare 3.2 (3.x?) on Redhat 9 (any 2.4.20+ kernel?) Lucas Correia Villa Real
2003-04-17 16:48   ` [patch] VMnet/VMware workstation 4.0 Lucas Correia Villa Real
2003-04-17 20:08 ` Small fix for VMWare 3.2 (3.x?) on Redhat 9 (any 2.4.20+ kernel?) wwp

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=E193vrp-0006P4-00@trillium-hollow.org \
    --to=erich@uruk.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).