GunLink Software Release Notes 3.1.1 patches

Patches are cumulative - that is you only ever need the latest one installed, you do not need to install intermediate versions. Patches are specific to the GunLink release number they will only install on that release.

But if you ever need to unroll one or more patches then this will take you back to the original major release. If you wanted to go back to the previous version of a patch you will need to re-install that after unrolling.

Patches are stored in /opt/gunlink/patches/patchname. Within each patch directory you can find a copy of the latest patch file that you can use to unroll it (or any previous version), a copy of the release notes, a file containing the patch release date and the backup files. These directories do not get deleted even if you unroll a patch.

Installation

The patch file name will be something like 3p1p1-21december2011.bin.gz for example. In these notes replace 'xxxx' with in this case '3p1p1-21december2011'. The directory created will be /opt/gunlink/patches/3p1p1 replace 'yyyy' with this.

• Copy the distribution file which will have a .bin.gz extension to a USB memory stick and insert that in the host machine, a desktop icon should appear.
• open a terminal and become root using 'su -', you must use this command not just 'su'.
• Copy the file to root's home directory. The USB stick will be mounted as '/media/disk/' or possibly '/media/USBsomething' look at the desktop icon to see what the name is. 'cp /media/disk/xxxx.bin.gz ./'
• Check the file checksum for corruption 'sha1sum xxxx.bin.gz' the correct value should have been given to you when you got the file.
• Unzip the file 'gunzip xxxx.bin.gz' this will unzip the file and remove the '.gz' extension.
• Check the checksum again using the other value you were given 'sha1sum xxxx.bin'
• Ensure the file is executable 'chmod u+x xxxx.bin'
• Install it './xxxx.bin', read the release notes and reboot as required. If you have a previous patch for this release installed you will be prompted to overwrite it.
• Use updateAllFirmware to update any new firmware (see the operator's manual).
• Repeat installation on spare host machine and any remote display machine.

Unrolling

To unroll a patch and restore the system to the base install:

• open a terminal and become root using 'su -', you must use this command not just 'su'.
• Change to the patch directory 'cd /opt/gunlink/patches/yyyy'
• Execute the patch file with the '--unroll' option. './xxxx.bin --unroll'
• If you need to revert to a previous patch version you need to re-install it now.
• Reboot the machine and all GCUs or TEMS.
• Unroll the same patch on the spare machine and any remote display machines.

Determining patch version (if any)

From release 3.1.1 patches will be visible in the panel applet main status window which will show the main version '3.1.1' for example and the patch date. If there is no patch date there is none installed. You can also look in the 'documents' section of GunLink Web, if no patch release notes are shown no patches are installed.

Instrument tests - Fix - Saved instrument test files were not visible to be reloaded although the files were sucessfully saved and could be seen on disk - in /opt/gunlink/var/itests/Results.

Instrument tests - Fix - Frequency plots had linear scales rather than the previous and intended log scale.

Instrument tests - Fix - Very small values (in noise plots for example) displayed as zero in plot scale markings.

Instrument tests - Change - Saved instrument test data file names were not legal on Windows file systems so needed to be renamed if copied to FAT formatted USB sticks or other locations. The original file format was yyy_mm_dd-hh:mm:ss.xml this is changed to itest-yyymmdd-hhmmss.xml which is the same date and time format as used for other log files. Display will list both old and new name format files and reload them as required. Results files are in /opt/gunlink/var/itest/Results.

'runjava' service script - Fix - The system would hang on rebooting if you tried to do a 'demo' install. Also when restarting after installing an archive from a release 2 machine. In both cases the system operates correctly if you kill the system and restart. The problem was a continuous loop while updating old configuration files. If you install the patch before loading a release 2 archive the problem should not now occur but this cannot help the 'demo install' case as you cannot easily install the patch before the demo archive is installed.

Create log files - Fix - The buttons for creating log and 'all messages' files were swapped, the 'all messages' button created a seismic log and VV.

Patch release notes - for this patch.

Release notes - Updated - added a description of the changed behaviour of timing link status LEDs to the 3.1.1 release notes.

19/12/2011 - Latest licence file - 19 December 2011.