9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Tharaneedharan Vilwanathan" <vdharani@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] vmware fusion - plan9 snarf issue
Date: Fri,  2 Jan 2009 15:51:24 -0800	[thread overview]
Message-ID: <dac0a5820901021551q9c89ecndb993bbc24e8f856@mail.gmail.com> (raw)
In-Reply-To: <509071940812280644h21ad5a00sa30f462c0f6dd223@mail.gmail.com>

hi anthony/russ,

okay, this is what i see now:

- with stand-alone kernel, i do see the snarf issue as i mentioned.
- however, i completed the installation to make it auth/cpu server. i
think i added a couple of devices in the config file, built the image
and used it for booting as auth/cpu server. i no longer see the
cut-and-paste issue now. i dont really know what did the trick but i
am very happy to see that the problem went away.

btw, i meant cut-and-paste within plan9 within the same VM. for now, i
am not worried about cut-and-paste for copying in and out of VM.

thanks
dharani
On Sun, Dec 28, 2008 at 6:44 AM, Anthony Sorace <anothy@gmail.com> wrote:
> to be clear, this behavior is while running the old plan 9 vmware
> tool, right? without that, i'd expect the snarf buffer to work
> properly within the guest environment, but you won't have any way to
> get things out.
>
>



  reply	other threads:[~2009-01-02 23:51 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 [this message]
2009-01-03 18:21   ` Skip Tavakkolian
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=dac0a5820901021551q9c89ecndb993bbc24e8f856@mail.gmail.com \
    --to=vdharani@gmail.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).