From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] vmware fusion - plan9 snarf issue
Date: Sat, 3 Jan 2009 10:21:27 -0800 [thread overview]
Message-ID: <4d1edbda0c81bc50830fb5e6e597f189@9netics.com> (raw)
In-Reply-To: <dd6fe68a0812270901l4b8fcbf3u33495721656e3d9f@mail.gmail.com>
>> 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. from what i
can tell the old backdoor (low bandwidth) mechanism is still supported
and the protocol hasn't changed. there's an alternative high
bandwidth mechanism but i'm not sure if the advent of the high
bandwidth rpc was later than plan9's vmware tools (Russ?).
i setup a new vm (workstation v. 6.5.1) and installed from the latest
iso image and compared it to my existing vm (4.5.3) running an older
kernel. the results from directly io to /mnt/vmware/snarf are the
same as far as i can tell. this pattern is consistent: the snarf
buffer of the Plan 9 guest can be made visible in Windows host
consistently ONLY if in Plan 9 guest, the snarf file is read before
writing to it. that is:
cat /mnt/vmware/snarf
echo 1 > /mnt/vmware/snarf
then the host and the guest os clipboard correctly reflect the last snarfed piece.
-Skip
[1] http://open-vm-tools.sourceforge.net/
the low level parts referenced in vmwarefs can be found under:
lib/backdoor
lib/guestApp (getdeviceinfo)
toolbox/ (get/setguistate)
next prev parent reply other threads:[~2009-01-03 18:21 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 [this message]
2009-01-03 18:57 ` Russ Cox
2009-01-03 21:33 ` Roman V. Shaposhnik
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=4d1edbda0c81bc50830fb5e6e597f189@9netics.com \
--to=9nut@9netics.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).