From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Fg7DC-00071Z-Gw
	for qemu-devel@nongnu.org; Tue, 16 May 2006 17:36:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Fg7DB-00071F-4I
	for qemu-devel@nongnu.org; Tue, 16 May 2006 17:36:14 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Fg7DA-00071C-Pz
	for qemu-devel@nongnu.org; Tue, 16 May 2006 17:36:12 -0400
Received: from [209.234.73.39] (helo=narn.hozed.org)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Fg7Ft-0005Wm-Hi
	for qemu-devel@nongnu.org; Tue, 16 May 2006 17:39:01 -0400
Date: Tue, 16 May 2006 16:36:11 -0500
From: Troy Benjegerdes <hozer@hozed.org>
Subject: Re: [Qemu-devel] qemu vnc.c vnchextile.h
Message-ID: <20060516213611.GZ15855@narn.hozed.org>
References: <E1FfL4I-0003wK-0G@savannah.gnu.org>
	<20060516152657.GT15855@narn.hozed.org>
	<446A19B8.4070309@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
In-Reply-To: <446A19B8.4070309@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> >Chicken of the vnc on MacOS X 
> >
> >http://sourceforge.net/projects/cotvnc/
> >  
> 
> Can you provide a bit more info on what you mean by troubles?
> 
> Regards,
> 
> Anthony Liguori

I found a wonderfull little tool called 'rfbproxy'. It, and saved
sessions of the bogus behavior with chickenofthevnc are at:

http://scl.ameslab.gov/~troy/qemu

Also, can I make a feature request that 

'info vnc' 

in the qemu monitor return all the appropriate connection information,
including bit depth, encoding, etc?