Getting Started with Thinstation
Clone this wiki locally
Choosing a build environment
First of all you have to set up a Thinstation build environment for boot images. You can choose between either
- a pre-configured, dedicated Linux installation called “DevStation” and
- a standard Linux installation of your choice. Read on for further instructions.
Cloning the Thinstation Git repository
Let’s assume you chose the second option from above. Then you need a reasonably modern Linux installation with Git installed.
Start up a shell window and run:
git clone --depth 1 git://github.com/Thinstation/thinstation.git -b 5.5-Stable
This will clone the current stable Thinstation branch into a newly created directory
Building a boot image
Enter the chroot building environment:
cd thinstation ./setup-chroot
This will take a few seconds. You will end up reading the file
README.md. Leave the pager application by pressing
Let’s move on with building your first Thinstation boot image:
cd build ./build
This will again take some time (up to a few minutes, depending on your system). In the subdirectory
boot-images three flavours of boot images get created. You could now go and boot either of these images, but they probably will be of no real use to you, because the standard configuration will not suite your needs.
If necessary you can use the
--kernel option of the
build script to choose a certain Linux kernel. Apart from
SMP for a SMP kernel (the default) you can choose from
UP for a uniprocessor kernel or
64 for a 64 bit only kernel. Example:
./build --kernel UP
After having seen how to build Thinstation boot images, it is time for you to adapt the configuration to your requirements. This involves
- deciding how to deploy Thinstation (how to boot up your thin clients),
- analysing the target hardware (where your boot image is intended to be run on),
- choosing the applications (or protocols) to be used by the end user and
- for each application defining the parameters (details on how it should operate). See here for further instructions.
From time to time you will want to update your repository.