Confirm
1,041
edits
Changes
no edit summary
# Open a shell and change the working directory to the application's installation directory by using the cd command. '''Important:''' running the update from within another directory will fail to update the existing installation properly with Firefox 3.6.x and below, SeaMonkey 2.0.x and below, and Thunderbird 3.1.x and below.
# It is recommended that all instances of the application that are running on the system including those being used by other users are closed before going any further. '''Important:''' though this should never cause the update to fail there might be cases where it will and it can definitely break a running instance of the application.
# For Firefox 34.x and above, SeaMonkey 2.31.x and above, or Thunderbird 34.x and above run the following from the command prompt. The additional <code><path to installation directory></code> is used by applications when applying staged updates and when manually applying a mar the value must be the installation directory.<br><pre><path to outside directory>\/updater <path to outside directory> <path to installation directory> <path to installation directory></pre><br>For Firefox 4.0.x and above, SeaMonkey 2.1.x and above, or Thunderbird 5.0.x and above run the following from the command prompt<br><pre><path to outside directory>/updater <path to outside directory> <path to installation directory></pre><br>For Firefox 3.5.x and 3.6.x, SeaMonkey 2.0.x, or Thunderbird 3.0.x and 3.1.x run the following from the shell<br><pre><path to outside directory>/updater <path to outside directory>/</pre><br>For Firefox 3.0.x or Thunderbird 2.0.x run the following from the shell<br><pre><path to outside directory>/updater <path to outside directory>/ 0</pre>'''Note:''' The "0" parameter passed on the command line specifies the PID of a process to wait on before applying the update. When applying updates manually this should be 0 to disable the wait step.
# After the update has completed a file named <code>update.status</code> will be created in the '''outside''' directory. Open the <code>update.status</code> status file in an editor (e.g. vi). If the update is successful then the file will contain the text "succeeded". If it does not contain the text "succeeded", then the <code>update.log</code> file may be consulted to diagnose at what step the update failed. A failed update should leave the original application's installation intact.
