nanogui: is it possible? (NanoX + eCos, PC)
Subject:
Re: [nanogui] is it possible? (NanoX + eCos, PC)
From:
Vladimir Sterjantov ####@####.####
Date:
27 Jun 2002 05:44:27 -0000
Message-Id: <3D1AA395.3030309@tersy.ru>
Thank You very much for explanation and interesting information.
-- Vladimir
Alex Holden wrote:
> Vladimir Sterjantov wrote:
>
>> linux # export DISPLAY=target_eCos_NanoX_PC:0.0
>> linux # nanokbd
>> Does NanoX have this functionality of X11 ?
>
>
> My CVS snapshot has TCP/IP networking functionality on Linux, however
> it probably won't work "out of the box" on ecos.
>
> You can get my snapshot from:
> http://www.linuxhacker.org/cvs-snapshots/microwin-aph/
>
> Greg is working on merging my tree with his at the moment in order to
> make a new release eventually.
>
> After compiling with SUPPORT_TCP_IP=Y, start the nano-X server with
> the "-t port" command line option and start the clients with the
> environment variable "NXDISPLAY=server:port" set, where "server" is
> the IP or hostname of the remote server and "port" is the service name
> or number of the TCP port to use.
>
> Beware that there is no security at all with this feature. You should
> only ever use it on a trusted network.
>
> You can however start nano-X with -l as well as -t port, which will
> cause it to only accept connections from localhost. This feature is
> useful to support ssh tunnelling (whereby the ssh daemon accepts an
> encrypted TCP stream and relays it to the server on the local host),
> without allowing people to make unencrypted connections from other
> machines.
>
> There is a related feature, whereby you can start the server with "-n
> /path/to/named/socket" and start the client with
> "NXDISPLAY=/path/to/named/socket" (which overrides the default
> /tmp/.nano-X). This allows you to have several Nano-X servers using
> named sockets on the same machine without them treading on one another.
