From: Philippe Anel <philippe.anel@noos.fr>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Get the message number (aux/vmware fix ?)
Date: Mon, 26 Apr 2004 17:39:56 +0200 [thread overview]
Message-ID: <6.0.0.22.0.20040426172524.0aca9040@pop.noos.fr> (raw)
In-Reply-To: <ccb0c59e71d13c62c42b6ec7e5528457@mteege.de>
At 17:15 26/04/04, you wrote:
>On Mon Apr 26 14:50:01 GMT 2004, philippe.anel@noos.fr wrote:
> > Ok, it seems you disabled Cut and Paste from and to the virtual
> > machine. Right ?
>
>Yes, because there are problems with other apps.
>
> > I suspect a bug from aux/vmwarefs which fails to back copy to
> > /dev/snarf, the value written to /mnt/vmware/snarf, when Cut
> > and Paste is disabled from and to the virtual machine.
> > Could you try the following aux/vmware script :
>
>H run your script with cut/paste enabled and disabled in vmware.
>
>VMware c/p enabled
>term% ./srf
>starting vmwarefs
>binding /mnt/vmware/snarf over /dev/snarf
>starting vmmousepoll
>
>VMware c/p disabled
>term% ./srf
>starting vmwarefs
>starting vmmousepoll
>
>In both cases snarf/paste from rio to sam or acme don't work.
:(
Did you rebooted the vm between each test ?
Could you execute this script from termrc (ie before rio) ?
Could you execute the command "/bin/ns | grep snarf" after each test ?
Regards,
Philippe.
>Matthias
next prev parent reply other threads:[~2004-04-26 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 8:11 [9fans] Get the message number Matthias Teege
2004-04-26 8:28 ` Philippe Anel
2004-04-26 9:48 ` Matthias Teege
2004-04-26 10:23 ` Philippe Anel
2004-04-26 11:00 ` Matthias Teege
2004-04-26 14:28 ` [9fans] Get the message number (aux/vmware fix ?) Philippe Anel
2004-04-26 15:15 ` Matthias Teege
2004-04-26 15:39 ` Philippe Anel [this message]
2004-04-26 16:45 ` Matthias Teege
2004-04-26 17:50 ` Philippe Anel
2004-04-27 5:43 ` Matthias Teege
2004-04-27 6:09 ` Matthias Teege
2004-04-27 8:48 ` Philippe Anel
2004-04-27 10:58 ` Matthias Teege
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=6.0.0.22.0.20040426172524.0aca9040@pop.noos.fr \
--to=philippe.anel@noos.fr \
--cc=9fans@cse.psu.edu \
/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).