From: Daniel Gryniewicz <dang@fprintf.net>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Lucas Correia Villa Real <lucasvr@gobolinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] VMnet/VMware workstation 4.0
Date: 17 Apr 2003 15:28:37 -0400 [thread overview]
Message-ID: <1050607717.2477.9.camel@athena.fprintf.net> (raw)
In-Reply-To: <D79F957BFD@vcnet.vc.cvut.cz>
On Thu, 2003-04-17 at 14:12, Petr Vandrovec wrote:
> On 17 Apr 03 at 13:48, Lucas Correia Villa Real wrote:
>
> > Is there a "correct" place at vmware.com to send these patches? I tryied
> > sending it to feature-request@vmware.com, but I got no response from them.
> >
> > Anyway, below follows the patch providing support to devfs on the vmnet driver
> > for vmware workstation 4.0.
>
> You can send them to me if you do not trust feature-request...
>
> Proble with your patch is that it does not look like that it will
> build on 2.2.x without complaints, but I can fix that. More important
> question to me is: do people really use devfs?
>
> And if change will not make into next WS release, I can always distribute it
> from my site.
> Petr Vandrovec
Gentoo uses devfs, and some people (like me) use VMware on gentoo. Not
that this matters, because the vmware startup files make the correct
device nodes. (I've never used vmware on non-devfs but I assumed it
works fine there.)
Daniel
--
Daniel Gryniewicz <dang@fprintf.net>
next prev parent reply other threads:[~2003-04-17 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 18:12 [patch] VMnet/VMware workstation 4.0 Petr Vandrovec
2003-04-17 19:28 ` Daniel Gryniewicz [this message]
2003-04-18 18:10 ` Lucas Correia Villa Real
-- strict thread matches above, loose matches on Subject: below --
2003-04-11 10:34 Small fix for VMWare 3.2 (3.x?) on Redhat 9 (any 2.4.20+ kernel?) erich
2003-04-16 4:42 ` Lucas Correia Villa Real
2003-04-17 16:48 ` [patch] VMnet/VMware workstation 4.0 Lucas Correia Villa Real
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=1050607717.2477.9.camel@athena.fprintf.net \
--to=dang@fprintf.net \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lucasvr@gobolinux.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).