GitBook: [master] 44 pages modified

Author: chewitt

support/update.md

@@ -1,20 +1,25 @@
 # Updating
 
-Updating LibreELEC is \(mostly\) simple and can be done automatically, manually from inside the Kodi GUI via the LibreELEC Settings Add-On, or by copying an update file to a local Samba share, or from the SSH console.
+Updating LibreELEC is \(mostly\) simple and can be done automatically, manually from inside the Kodi GUI via the LibreELEC Settings add-on, by [downloading an update file from our website](https://libreelec.tv/downloads_new) and copying the file to a local Samba share, or by running a command from the SSH console. We publish two image file types:
+
+* LibreELEC-Project.arch-9.6.7**.tar** \(update\) files which are used for updates only.
+* LibreELEC-Project.arch-9.6.7**.img.gz** \(image\) files which are used for creating new USB/SD installation media but can also be used for updates.
+
+We can update from both .tar/.img.gz files, but .tar files are faster to process.
 
 ## Auto-Update
 
-Auto-Update is enabled by default and tracks minor version updates, e.g. LibreELEC 9.2.0 will update to 9.2.1, 9.2.2, etc. as they are released. It will not perform major version updates as these involve Kodi add-on updates and user-experience changes that we do not want to force onto users. If auto-update is on the latest update file will download in the background, then Kodi will prompt you to reboot and start the update process. If you prefer to manage updates manually, auto-update can be disabled in the settings add-on.
+Auto-Update is enabled by default and tracks minor version updates, e.g. LibreELEC 9.2.0 will update to 9.2.1, 9.2.2, etc. as they are released. It will not perform major version updates as these involve Kodi add-on updates \(roken add-ons are the source of most update issues\) and user-experience changes that we do not want to force onto users. If auto-update is enabled the latest update file will download in the background, then Kodi will prompt you to reboot and start the update process. If you prefer to manage system updates manually, auto-update can be disabled in the settings add-on.
 
 ## Setttings Add-On
 
-Navigate to the Update section of the settings add-on, select the update channel and then the specific version to update to. The update .tar file will start downloading, and once complete, LibreELEC will reboot to perform the update. Please see the following video:
+Navigate to the Update section of the settings add-on, select the update channel \(LibreELEC major version\) and then the specific minor version to update to. The update .tar file will start downloading, and once complete the system will reboot to perform the update. 
 
-[https://www.youtube.com/embed/CjlHY6syRHw](https://www.youtube.com/embed/CjlHY6syRHw)
+Please see the following video: [https://www.youtube.com/embed/CjlHY6syRHw](https://www.youtube.com/embed/CjlHY6syRHw)
 
 ## Samba Share
 
-We publish two image file types; .img.gz files which can be used for new installations and updates, and .tar files which are only used for updates \(and are faster to update from\). Download the update file from [https://libreelec.tv/downloads\_new](https://libreelec.tv/downloads_new) and using a file browser, copy/paste it to the `\\LIBREELEC\UPDATE` Samba share on your LibreELEC device. Once the file transfer has completed, reboot LibreELEC to start the update process.
+Using a file browser \(explorer.exe, not a web browser\) copy/paste an update file to the `\\LIBREELEC\UPDATE` Samba share on your LibreELEC device. Once the file transfer has completed, reboot LibreELEC to start the update process.
 
 ## SSH Console
 
@@ -44,25 +49,25 @@ reboot
 
 ## Downgrade
 
-Kodi does not support downgrading. If "updating" within the same release, e.g. LibreELEC 9.2.6 to 9.2.5, the downgrade will normally work. If downgrading e.g. LibreELEC 9.2.6 to 9.0.2, the downgrade process will complete but Kodi may not gracefully handle being restarted with configuration files and add-ons from the \(newer\) previous release. To successfully downgrade, you must take a backup before updating, then clean install and restore the backup.
+Kodi does not support downgrading. If "updating" within the same LibreELEC/Kodi major release, e.g. LibreELEC 9.2.6 to 9.2.5, the downgrade will normally work. If downgrading to an older LibreELEC/Kodi major version e.g. LibreELEC 9.2.6 to 9.0.2, the downgrade process will complete but Kodi may not gracefully handle being restarted with configuration files and add-ons from the \(newer\) previous release. Always make a backup before upgrading so that you can clean install then restore the backup to effect a downgrade without problems.
 
 ## Migrate OpenELEC
 
-In 2016 when we forked from OpenELEC the differences between projects were small and it was deliberately simple to migrate by using our update .tar file. Today there are some challenges:
+In 2016 when we forked from OpenELEC the differences between projects were small and it was simple to migrate by using our update .tar file. Today there are some challenges:
 
-* LibreELEC images for Generic x86\_64 hardware are now 240MB+ in size and most OpenELEC installs have a 230MB boot partition so LibreELEC files do not fit and the update process will fail \(gracefully\). Raspberry Pi and similar images are smaller and will still fit, but read on:
-* Older Kodi add-ons are frequently incompatible with newer Kodi versions, causing crashes when the system restarts. We detect when Kodi repeatedly fails to start and will run with a "safe mode" configuration, but this normally requires SSH console fiddling to get back to a working setup.
-* Kodi does not self-manage media and add-on package caches so over-time filesystem litter accumulates. Starting from a clean install removes all the file junk resulting in a faster/lighter installation with an improved Kodi user experience.
+* LibreELEC images for Generic x86\_64 hardware are now 240MB+ in size and most older OpenELEC installs have a 230MB boot partition so LibreELEC files will not fit and the update process will fail \(gracefully\). Raspberry Pi and similar images are smaller and will still fit, but read on:
+* Older Kodi add-ons are frequently incompatible with newer Kodi versions, causing crashes when the system restarts, and the bigger the version jump the more likely add-ons will cause problems. LibreELEC will detect when Kodi repeatedly fails to start and will run with a "safe mode" configuration, but this normally requires SSH console fiddling to get back to a working setup.
+* Kodi does not self-manage media and add-on package caches so over-time filesystem litter accumulates. Starting from a clean install removes all the not-needed junk resulting in a faster/lighter installation with an improved Kodi user experience.
 
-To migrate essential Kodi data from the old installation, stop Kodi and back-up the userdata folder:
+To migrate essential Kodi data from the old installation before migrating \(which is likely to fail\) or making a clean installation, stop Kodi and back-up the userdata folder:
 
 ```text
 cd /storage/backup
 systemctl stop kodi
 tar -czf kodi_userdata.tar.gz /storage/.kodi/userdata
 ```
 
-Backup files are normally 1-2GB in size so move them off-box by copying to USB or copying from the `\\LIBREELEC\BACKUP` Samba share. After installing LibreELEC you can restore the backup:
+Backup files are normally 1-2GB in size so move them off-box by copying to USB or moving them to `/storage/backup` which is accessible over the network via the `\\LIBREELEC\BACKUP` Samba share. After installing LibreELEC you can restore the backup:
 
 ```text
 systemctl stop kodi
@@ -71,7 +76,5 @@ tar -xzf /storage/kodi_userdata.tar.gz
 systemctl start kodi
 ```
 
-The following video shows the migration process from OpenELEC v7.0 to LibreELEC v7.0. The Kodi GUI now looks different but the process remains the same:
-
-[https://youtu.be/Tkoxg-Q0Fe8](https://youtu.be/Tkoxg-Q0Fe8)
+The following video shows the migration process from OpenELEC v7.0 to LibreELEC v7.0 as it looked in 2016. The Kodi GUI now looks different \(the skin changed\) but the process remains the same: [https://youtu.be/Tkoxg-Q0Fe8](https://youtu.be/Tkoxg-Q0Fe8)