Solving the problem with non-bootable configs in Thinstation 5
Good day, Habr.
In the fifth version of Thinstation there is such a very unpleasant bug - a booting thin client works only on the basic configuration and doesn’t see the configs which should be pulled over the network. The problem is aggravated by the fact that there is no single solution to this problem on the Internet - they offer different ways on different resources, turning over which, constantly changing settings, a person accidentally solves the problem and forgets about it for a long time.
In this mini-article, I want to collect those nuances of settings that solve this problem.
')
So, we consider the case when we already have a thinstation installed, the thin client successfully connects and works, but with the loading of named configs - deafly. All initial configuration is performed in two configs: build.conf and thinstation.conf.buildtime . The good instruction on assembly and setup is on Habré (he used it), I will stop on critical points.
turn on
turn off
This is the case when the system works with all versions of these options, and the correct version is found either by typing or by directly asking the soap developer.
necessarily
Although all the prompts in vain write that these parameters can be used at any stage in any configuration files, their presence is necessary precisely in the default config that is stitched into the downloadable image. The last parameter is the most offensive: it is almost not found in the documentation and examples of configs and it should take the value of the ip-address of the server from which the download is made, regardless of whether you use dhcp or not.
All is ready! Now the thin client will run and pick up configs from the server, as intended.
Have a good job. ;)
In the fifth version of Thinstation there is such a very unpleasant bug - a booting thin client works only on the basic configuration and doesn’t see the configs which should be pulled over the network. The problem is aggravated by the fact that there is no single solution to this problem on the Internet - they offer different ways on different resources, turning over which, constantly changing settings, a person accidentally solves the problem and forgets about it for a long time.
In this mini-article, I want to collect those nuances of settings that solve this problem.
')
Introductory
So, we consider the case when we already have a thinstation installed, the thin client successfully connects and works, but with the loading of named configs - deafly. All initial configuration is performed in two configs: build.conf and thinstation.conf.buildtime . The good instruction on assembly and setup is on Habré (he used it), I will stop on critical points.
build.conf
turn on
- ts-classic
- ssh (if you will use image loading via scp)
turn off
- networkmanager
- udisks-glue
This is the case when the system works with all versions of these options, and the correct version is found either by typing or by directly asking the soap developer.
thinstation.conf.buildtime
necessarily
- NET_FILE_ENABLED = On
- NET_FILE_METHOD = tftp / scp
- NET_FILE_ALTERNATE = xh.xxx.xxx.xx
Although all the prompts in vain write that these parameters can be used at any stage in any configuration files, their presence is necessary precisely in the default config that is stitched into the downloadable image. The last parameter is the most offensive: it is almost not found in the documentation and examples of configs and it should take the value of the ip-address of the server from which the download is made, regardless of whether you use dhcp or not.
All is ready! Now the thin client will run and pick up configs from the server, as intended.
Have a good job. ;)
Source: https://habr.com/ru/post/221513/
All Articles