From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org (Linux-KERNEL)
Subject: Re: VMWare will not run on kernel 2.4.0-test11
Date: Thu, 23 Nov 2000 22:29:50 MET-1 [thread overview]
Message-ID: <DB4EB260F6F@vcnet.vc.cvut.cz> (raw)
On 23 Nov 00 at 20:22, Alan Cox wrote:
> > vmware-2.0.3-786 refused to run. Running vmware-config.pl resulted in a
> > the following message:
>
> Run 2.4.0-test11-ac3
Hi Alan,
is change to field name temporary, and name will be reverted back
to flags, even although contents may differ between 2.2.x and 2.4.x,
or is there features to stay? Currently VMware does
"^\(features\|flags\).* tsc"
but question is - should we leave it here, or revert it back?
BTW, as I told couple of times here, if you have problem with VMware
on 2.3.x/2.4.x kernel, please first visit news server news.vmware.com
and look into vmware.for-linux.experimental newsgroup. If you'll not
find fix/workaround here (this one is there since Tigran pointed it to
me more than week ago - Nov 15, 02:59 CET), post question to that forum.
I watch that newsgroup almost continuously during my working hours (that
is aprox. 12:00-24:00 CET Mon-Fri).
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-23 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 22:29 Petr Vandrovec [this message]
2000-11-23 22:15 ` VMWare will not run on kernel 2.4.0-test11 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-11-23 20:07 Phil Stracchino
2000-11-23 20:15 ` Mohammad A. Haque
2000-11-23 20:17 ` Phil Stracchino
2000-11-23 20:18 ` Jan Dvorak
2000-11-23 20:22 ` Alan Cox
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=DB4EB260F6F@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--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