GunLink Software Release Notes 3.1.0 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 3p1p0-21june2011.bin.gz for example. In these notes replace 'xxxx' with in this case '3p1p0-21june2011'. The directory created will be /opt/gunlink/patches/3p1p0 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.

If you have not previously installed the 16th May version of this patch then the new firmware included in this patch must be installed by the operator using 'updateAllFirmware' as normal.

master - Fix - If you selected only 'long phones' for recording to SEG-D files the writeSegd process was not started and no SEG-D files created. Looking at the GunLink panel app process status writeSegd was grey and marked as 'not required'. If you selected some other channel type for recording in addition to 'long phones' the system operated correctly. It also operated correctly if you selected some additional channel type then changed to just long phones but would then fail again at the next restart of the host programs.

21/06/2011 - Latest licence file - 21 June 2011.

The new firmware included in this patch must be installed by the operator using 'updateAllFirmware' as normal.

ad - Fix - Bug caused the day of the year in the nodes to be wrong for up to 5 minutes after midnight resulting in spurious fire time mismatch messages when compared to the TCU time stamp which had the correct day number.

adread - Fix - The timer used to control system timeouts could run slowly. In particular it can result in incorrect 'arm to fire delay too short' messages when using an arm to fire delay of 1 second or less.

adread - Fix - When using the new 'long hydrophone' capability of SEG-D recording with a record length less than the shot cycle time a warning that hydrophone coverage is not continuous was issued to the log. Setting the record length to for example match the seismic record length is a legitimate use of the feature so it is not an error. Message downgraded to 'info'.

tcucom - Expanded some debug messages in case of further problems with timeout timer.

TCU1p4p10 When running on internal 1PPS - with GPS not fixing or not connected - the node clocks were 18.75uS out of sync resulting in fire time mismatch error messages. The time stamps recorded in the headers and database from the TCU were correct.

Install using 'updateAllFirmware -T'

13/05/2011 - Latest licence file - 13 May 2011.