-
-
Notifications
You must be signed in to change notification settings - Fork 189
Using the hdupdate package
If you use GRUB to boot ThinStation it is possible to make thin clients automatically update themselves via network.
In order to do so you have to identify each release of boot files with a version number. If the number on the server is newer than on a client, it will upgrade itself on bootup.
You need a HTTP (or TFTP or SCP) server for serving the kernel vmlinuz
and the initial ramdisk file initrd
.
Naturally one initial version of ThinStation including hdupdate needs to be installed on the thin client before automatic updates (carried out by hdupdate) can take place.
-
Uncomment
package hdupdate
inbuid.conf
. Set the familiy ofHDUPDATE
variables inthinstation.conf.buildtime
according to your configuration. For example:HDUPDATE_ENABLED=Y HDUPDATE_SERVER=172.16.0.98 HDUPDATE_SERVER_TYPE=wget HDUPDATE_PATH=/update HDUPDATE_WS_VERSION=1 HDUPDATE_TEMP=RAM HDUPDATE_FORCE=N
-
Build ThinStation and install this version on each client that should be updated through hdupdate.
-
Add at least the following variables to a network configuration file read by all clients in question:
HDUPDATE_SERVER_VERSION=1 HDUPDATE_FILES="initrd"
-
If a new release of your ThinStation boot files (
initrd
or even the kernelvmlinuz
) is due to be rolled out, you have to: -
Change
HDUPDATE_WS_VERSION
to a higher number and build ThinStation. -
Copy all necessary files (usually only
initrd
;vmlinuz
only if you switched to a newer ThinStation release/branch) to the HTTP/TFTP/SCP (depending onHDUPDATE_SERVER_TYPE
) servers directory. Put the files in the subdirectoryHDUPDATE_PATH
. -
Increase
HDUPDATE_SERVER_VERSION
to the same value as the latestHDUPDATE_WS_VERSION
. If a new kernel is to be delivered, changeHDUPDATE_FILES
to"initrd vmlinuz"
. -
Boot up all affected thin clients and check the update process. Note: The client will not reboot after a sucessful update but start up the previous version for the last time.