[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] RE: [PATCH][VT] add a new option for spawning vncviewer


  • To: "Edwin Zhai" <edwin.zhai@xxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 31 Aug 2005 09:20:20 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 31 Aug 2005 08:18:24 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcWt8If/ymHGIOISSb+vbEnkWd//iAAEvVKA
  • Thread-topic: [PATCH][VT] add a new option for spawning vncviewer

> > We should just spawn the viewer and put the details on the kernel 
> > command line, and leave it to the guest to start the server 
> and issue 
> > the vnconnect. See tools/examples/vnc/*
> how about this one?
> use -V command line but not "vncviewer" configuration, which 
> is suitable for both vmx and xenU.

I guess I agree that its slightly odd to have a configuration parameter
(as opposed to command line flag) that causes a viewer to be spawned. We
certainly don't have a config parameter that forces the equivalent of
'-c'. It does mean that most VT users will have to remember to put '-V'
on the command line, which is why I wouldn't object to retaining the
'vncviewer' configuration option. Let's see if anyone has strong views.

It's clear that we should put the hostip:port number where the
libvncserver is running somewhere into xenstore, so we can query it in
the same ay we do for console ttys.  

[Incidently, does anyone take objection to using '-V'? '-V' is sometimes
used to mean 'version', but I don't think that's a problem.]

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.