
Not long ago, a detailed
article appeared on Habrahabr about raising a terminal server to Linux. It is very attractive for its content and shows the ease of setting up such a solution.
Our network already has a similar solution based on Windows Server 2008 R2 with a separate TFTP server. And that was my problem. Below is a piece of config from PXE. For this, I ask for sweat cat.
')
LABEL ltsp KERNEL 10.0.20.8::/ltsp/i386/vmlinuz APPEND initrd=10.0.20.8::/ltsp/i386/initrd.img root=/dev/nbd0 nbdroot=10.0.20.8,2000 ip=dhcp selinux=0 init=/sbin/init-ltsp —
Since we use a third-party tftp-server, we must use a different format for uploading the image. It is easily googled by the word "oldstyle". Therefore, immediately after installing and configuring the server, as well as the contents of the clients, we do the
dpkg-reconfigure nbd-server and answer the questions:
- Maintain ports: Yes
- Number of copies: 1 (you may have more)
- Specify the path to the image: /opt/ltsp/images/i386.img
- Port number: 2000
- Export Name: Any (in my case ltsp)
Now, when booting the machine from the network, we see no errors and get an image of a client from NBD, which takes place on our machine. If you try to enter data for authorization, we will receive "
No response from the server, reboot ." And then the whole catch.
Again, when using a third-party tftp server, the contents of the
/ var / lib / tftpboot / ltsp / i386 / folder are ignored, respectively, and the
lts.conf config is ignored and all data for the client is listed. To fix this, we need to update the lts.conf that we use in the image. To do this, we go to
/opt/ltsp/i386/etc/lts.conf and specify everything there. In my case, this is the server address:
- SERVER = 10.0.20.8
- the rest of the lts.conf you can take in the original article
After the done procedures, we update the image with the
ltsp-update-image command and can connect from the terminals.
Special thanks I want to express to the author of the article about LTSP
@kvaps .