October 12, 2015 at 10:56Thinstation, connect to Linux terminal server via XDMCP
After reading the posts and manuals about Thinstation, you might get the impression that it is intended only for connecting to Windows servers via RDP in various ways, but I use it more and more often to organize terminals connecting to Linux-servers via XDMCP .
When switching to version 5, the developers decided to get rid of a direct connection to the X-server, which was set by the option " SESSION _ # _ TYPE = x ", now they advise using Xnest, but it is needed only to start the X-server in the window. I did not understand why this was done, I just noticed a minus in the fact that the connection systematically falls and the assembly swells to an extra 1.4 Mb. In recent versions, and so on, more and more kernel modules are integrated directly into it, as a result of which the image of the system takes longer and longer, so we do not need extra megabytes.
In order not to understand the causes and consequences of such a decision, the developers had to write their simple little “packet” for initializing a connection through a standard X server without spacers. I share ...
We create directories and files of our package, I have this xdmcp-connect :
In principle, the package is ready, now we add it to build.conf with the line package xdmcp-connect and in the file thinstation.conf.buildtime or in thinstation.conf.network we specify connection options:
Well, we allow XDMCP connection on the server.
I use Gnome as my desktop , so in the /etc/gdm/custom.conf file , in the [xdmcp] section , add:
And restart GDM , Xs or the server completely, to whom it is more convenient.
PS: If we see a black screen when trying to connect, we need to find the xnest command in the packages / base / etc / thinstation.packages file and replace it with xdmcp .
When switching to version 5, the developers decided to get rid of a direct connection to the X-server, which was set by the option " SESSION _ # _ TYPE = x ", now they advise using Xnest, but it is needed only to start the X-server in the window. I did not understand why this was done, I just noticed a minus in the fact that the connection systematically falls and the assembly swells to an extra 1.4 Mb. In recent versions, and so on, more and more kernel modules are integrated directly into it, as a result of which the image of the system takes longer and longer, so we do not need extra megabytes.
In order not to understand the causes and consequences of such a decision, the developers had to write their simple little “packet” for initializing a connection through a standard X server without spacers. I share ...
We create directories and files of our package, I have this xdmcp-connect :
cd /Ваша/папка/thinstation/ts/build/packages/
mkdir -p xdmcp-connect/etc/init.d
echo xorg7 > xdmcp-connect/dependencies
echo ",dependencies,0,0,,0,,,,,,,,," > xdmcp-connect/.dna
cd xdmcp-connect/etc/init.d
ln -s /etc/thinstation.packages xdmcp
In principle, the package is ready, now we add it to build.conf with the line package xdmcp-connect and in the file thinstation.conf.buildtime or in thinstation.conf.network we specify connection options:
SESSION_0_TYPE=xdmcp
SESSION_0_AUTOSTART=on
SESSION_0_XDMCP_SERVER=x.x.x.x # IP вашего сервера
SESSION_0_XDMCP_OPTIONS="X :3 -listen tcp -once -query"
Well, we allow XDMCP connection on the server.
I use Gnome as my desktop , so in the /etc/gdm/custom.conf file , in the [xdmcp] section , add:
Enable=true
And restart GDM , Xs or the server completely, to whom it is more convenient.
PS: If we see a black screen when trying to connect, we need to find the xnest command in the packages / base / etc / thinstation.packages file and replace it with xdmcp .
Only registered users can participate in the survey. Please come in.
How do you use Thinstation?
- 61.9% As a thin client for connecting to a Windows terminal server (Rdesktop, Freerdp, VNC, NX, etc.) 13
- 33.3% As a thin client for connecting to a Linux terminal server (XDMCP, NX, VNC, etc.) 7
- 4.7% As a kiosk with a web browser (Firefox, Chrome) 1
- 19% As a “fat client” with a window manager (IceWM, Xfwm, etc.) 4