Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: brunok on January 16, 2018, 08:18:08 AM
-
I'm excited about this distro! :P
I am currently trying to use X applications remotely.
I have a CentOS server, with 2 network cards. A NAT network delivering DHCP and a TinyCore 8.2 image remastered via TFTP.
Working very well!
I need to run X applications with DISPLAY redirection to TinyCore client IP.
On the server I did:
export DISPLAY=10.1.1.10:0.0
Where 10.1.1.10 is my Tiny Client with Xvesa. Already modified .xsession file (removed no tcp listen option).
And I tried running rdesktop on the server, to open it in TinyCore, but get error "could not open display".
Any idea?
-
Rdesktop is an application to connect to windows terminal server sessions (the open source equivalent of mstsc.exe) and is not what you want. Running X applications remotely is different. There are different ways to do it, but for the kind of setup you are describing you probably want to use XDMCP. It is a little more automagic than the other ways. Otherwise it is a manual process that a person would probably only do on an as-needed basis.
-
Rdesktop is one example.
I've installed XMING in a Windows BOX and open FIREFOX in my Server CentOS.
Firefox GUI running in Windows BOX, but process, running in my CentOS.
Example:
CentOS: export DISPLAY=x.x.x.x:0.0
firefox &
Where x.x.x.x is Windows IP.
In my TinyCore client, value of $DISPLAY is :0.0
But get error in my CentOS. :-\
Error: cannot open display: x.x.x.x:0.0
-
You may need to play with access control too (-ac option to Xvesa), or maybe Xorg.
edit: Tested with two Qemu instances in a LAN. Removing "-nolisten tcp" and adding "-ac -tcp", X remoting worked. Naturally disabling access control with -ac is insecure, so please set up a firewall or other measures.
-
ITS AMAZING!!!
Updated my .xsession with -ac and -tcp flags.
Work like a charm!
THANKS!