Thinstation, connect to Linux terminal server via XDMCP
After reading the posts and manuals about Thinstation, you may get the impression that it is intended only for connecting to Windows servers via RDP in various ways, but I’ve increasingly used it to organize terminals for connecting to Linux servers via XDMCP .
When switching to version 5, the developers decided to get rid of the direct connection to the X-server, which was set by the option " SESSION _ # _ TYPE = x ", now they are advised to use Xnest , and they only need it to start the X-server in the window. Why I did it, I did not understand it, only I noticed a minus in that the connection systematically falls and the assembly swells into an extra 1.4 MB. In the latest versions, more and more kernel modules integrate directly into it, as a result of which the image of the system loads longer and longer, so that extra megabytes are unnecessary to us.
In order not to understand the causes and consequences of such a decision, developers had to write their own simple “sachet” of connection initialization through a standard X-server without gaskets. I share ...
We create directories and files of our package, I have xdmcp-connect :
In principle, the package is ready, now we add it to build.conf with the package xdmcp-connect line and in the thinstation.conf.buildtime file or in the thinstation.conf.network we write connection options:
Well, we allow the server to connect via XDMCP.
I use Gnome as my desktop , so in /etc/gdm/custom.conf , in the [xdmcp] section, we add:
')
And restart GDM , X-s or the server completely, to whom it is more convenient.
PS: If we see a black screen when trying to connect, then you 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 the direct connection to the X-server, which was set by the option " SESSION _ # _ TYPE = x ", now they are advised to use Xnest , and they only need it to start the X-server in the window. Why I did it, I did not understand it, only I noticed a minus in that the connection systematically falls and the assembly swells into an extra 1.4 MB. In the latest versions, more and more kernel modules integrate directly into it, as a result of which the image of the system loads longer and longer, so that extra megabytes are unnecessary to us.
In order not to understand the causes and consequences of such a decision, developers had to write their own simple “sachet” of connection initialization through a standard X-server without gaskets. I share ...
We create directories and files of our package, I have 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 package xdmcp-connect line and in the thinstation.conf.buildtime file or in the thinstation.conf.network we write connection options:
SESSION_0_TYPE=xdmcp SESSION_0_AUTOSTART=on SESSION_0_XDMCP_SERVER=xxxx # IP SESSION_0_XDMCP_OPTIONS="X :3 -listen tcp -once -query" Well, we allow the server to connect via XDMCP.
I use Gnome as my desktop , so in /etc/gdm/custom.conf , in the [xdmcp] section, we add:
')
Enable=true And restart GDM , X-s or the server completely, to whom it is more convenient.
PS: If we see a black screen when trying to connect, then you need to find the xnest command in the packages / base / etc / thinstation.packages file and replace it with xdmcp .
Source: https://habr.com/ru/post/268635/
All Articles