wiki:upgrade_keros3_to_4
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
wiki:upgrade_keros3_to_4 [2018/12/12 14:51] hch |
wiki:upgrade_keros3_to_4 [2019/02/14 14:55] hch [Limits] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Upgrade from KerOS 3.x to 4 with custom liveburner ====== | + | ====== Upgrade from KerOS version 3.x to 4.x with custom liveburner ====== |
| - | KerOS 4.x introduces some important modifications (new Kernel, rootfsRW, hotfixing) requiring an upgrade with a liveburner. This page will provide a way to do this upgrade with conservation of some elements like the configuration and reinstall some additional packages. | + | KerOS v4.x introduces some important modifications (new kernel, rootfsRW, hotfixing) requiring an upgrade with a liveburner. This page will provide a way to do this upgrade with conservation of some elements like the configuration and reinstall some additional packages. |
| ===== Introduction ===== | ===== Introduction ===== | ||
| - | A liveburner package will by default flash the eMMC content and install only the KerOS package. So any package, data and configurations will be lost using such upgrade package. \\ | + | A liveburner package will by default flash the eMMC content and install only the KerOS package. So any packages, data, and configurations will be lost using such upgrade package. \\ |
| - | This upgrade will be problematic for products already on the field that needs to keep a Device Management link UP and RUNNING before and after the upgrade. | + | This upgrade will be problematic for products already on the field that need to keep a Device Management link up and running before and after the upgrade. |
| To solve this, this procedure will provide: | To solve this, this procedure will provide: | ||
| Line 27: | Line 27: | ||
| ===== Requirements ===== | ===== Requirements ===== | ||
| - | * A desktop Linux machine (native or virtual) | + | * A desktop Linux machine (native or virtual). //=> It will be used to build the ''liveburner'' package.// |
| - | * An original KerOS liveburner 4.x package available in the [[wiki:resources|resources page]]. | + | * An original KerOS liveburner 4.x package available in the resources page: [[resources_ibts:resources|Wirnet iBTS resources]] or [[resources_ifemto:resources|Wirnet iFemtoCell resources]]. |
| - | * The ''update_liveburner_package-4.0-g8c53719.tar.gz'' tool available [[wiki:resources#other_tools|here]]. | + | * The ''update_liveburner_package-4.0-g8c53719.tar.gz'' tool available [[wiki:common_resources#tools|here]]. |
| - | * The following packages :<code bash>sudo apt-get install device-tree-compiler cpio binutils</code> | + | * The following packages: <code bash>sudo apt-get install device-tree-compiler cpio binutils</code> |
| ===== Limits ===== | ===== Limits ===== | ||
| Some limits are present in this upgrade mechanism: | Some limits are present in this upgrade mechanism: | ||
| - | * Safezone space: 2MiB | + | * Safezone space: 2MiB. |
| - | * Additional packages max size cumulated: 20MiB | + | * Additional packages max size cumulated: 20MiB. |
| - | * Secure Storage is lost for products without Secure Boot activated | + | |
| ===== Usage ===== | ===== Usage ===== | ||
| Line 67: | Line 67: | ||
| Additional packages can be installed simply by adding them as arguments. | Additional packages can be installed simply by adding them as arguments. | ||
| <code bash> | <code bash> | ||
| - | ./update_liveburner.sh liveburner_4.0.2_klk-lpbs-signed.ipk preinst preapps my_packet.ipk | + | ./update_liveburner.sh liveburner_4.0.2_klk-lpbs-signed.ipk preinst preapps my_package.ipk |
| </code> | </code> | ||
| </note> | </note> | ||
| Line 90: | Line 90: | ||
| ++++ | ++++ | ||
| - | File to download - Preinst.sh | | + | File to download - preinst.sh | |
| <code bash preinst.sh> | <code bash preinst.sh> | ||
| #!/bin/sh | #!/bin/sh | ||
| Line 155: | Line 155: | ||
| ++++ | ++++ | ||
| - | In case of customer blocking problem during the execution of this script, it is possible to interrupt the upgrade. To do so, it is possible to use the function **fatal_error** in the customer part of the script like this: | + | In the case of custom upgrade blocking problem happens during the execution of this script, it is possible to interrupt the upgrade. To do so, it is possible to use the function **fatal_error** in the custom part of the script like this: |
| <code bash> | <code bash> | ||
| cp ${ROOTFSRW_PATH}/etc/non_existant_file ${SAFEZONE_MOUNTPOINT}/ || fatal_error "Error detected! stop the upgrade!!" | cp ${ROOTFSRW_PATH}/etc/non_existant_file ${SAFEZONE_MOUNTPOINT}/ || fatal_error "Error detected! stop the upgrade!!" | ||
| Line 174: | Line 174: | ||
| ++++ | ++++ | ||
| - | File to download - Preapps.sh | | + | File to download - preapps.sh | |
| <code bash preapps.sh> | <code bash preapps.sh> | ||
| #!/bin/sh | #!/bin/sh | ||
