From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] vmware fusion - plan9 snarf issue
Date: Sat, 3 Jan 2009 13:33:16 -0800 [thread overview]
Message-ID: <1231018396.11463.196.camel@goose.sun.com> (raw)
In-Reply-To: <4d1edbda0c81bc50830fb5e6e597f189@9netics.com>
On Sat, 2009-01-03 at 10:21 -0800, Skip Tavakkolian wrote:
> >> snarf doesnt work properly in plan9 on vmware fusion 2.0 for mac. from what
> >> i found this seems to be a known issue. is there any fix available?
> >
> > no; someone needs to write a new version
> > of the vmware tools that works with the latest
> > vmware versions.
> >
> > russ
>
> i've been reviewing open-vm-tools[1] and Russ' vmwarefs.
Where's the source code for vmwarefs located?
Thanks,
Roman.
next prev parent reply other threads:[~2009-01-03 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 9:24 Tharaneedharan Vilwanathan
2008-12-27 17:01 ` Russ Cox
2008-12-28 12:09 ` Tharaneedharan Vilwanathan
2008-12-28 14:44 ` Anthony Sorace
2009-01-02 23:51 ` Tharaneedharan Vilwanathan
2009-01-03 18:21 ` Skip Tavakkolian
2009-01-03 18:57 ` Russ Cox
2009-01-03 21:33 ` Roman V. Shaposhnik [this message]
2009-01-03 21:46 ` Russ 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=1231018396.11463.196.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).