9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.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 10:57:55 -0800	[thread overview]
Message-ID: <dd6fe68a0901031057x75bc3709gb580716c54a56b70@mail.gmail.com> (raw)
In-Reply-To: <4d1edbda0c81bc50830fb5e6e597f189@9netics.com>

> 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?).

it happened about the same time.
there is support for the high bandwidth
channel -- read and write /mnt/vmware/msg.

> 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

interesting.  maybe that's worth making a new binary.

russ


  reply	other threads:[~2009-01-03 18:57 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 [this message]
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=dd6fe68a0901031057x75bc3709gb580716c54a56b70@mail.gmail.com \
    --to=rsc@swtch.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).