This page explains system upgrades on KerOS >= v.4 and also:

• Configuration management (sysupgrade).
• Hotfix packages management during upgrades.

The firmware is released in two formats: KerOS: and Liveburner. These have very different behavior, so please use the appropriate file before updating, see the difference in upgrade process section.

To upgrade the system from KerOS version 3.x to KerOS version 4.x the use of a liveburner is mandatory. Two possibilities are available:

• Upgrade with conservation of some elements like the configuration: please refer to this page to build a custom liveburner.
• Upgrade with a classic liveburner (erasing the whole partition to reinstall the firmware). Use the liveburner provided in the Wirnet iBTS resources page or Wirnet iFemtoCell resources page and the upgrade process below.

Upgrade system using a simple upgrade package (i.e. keros_4.X.Y_klk-lpbs-signed.ipk file) is only available from a source firmware version >= 4.0.

The upgrade will install the new KerOS firmware with some consequences on the data:

• User partition files will be preserved.
• Passwords will be preserved.
• The stock restore version will not be updated.
• RootFS modifications will NOT be kept except files indicated in sysupgrade configuration files

The upgrade process itself is the following sequence:

1. Backup files indicated in configuration (system files and software/customer defined files).
2. Remove hotfix packages.
3. Upgrade the system itself.
4. Restore sysupgrade files ⇒ will override new firmware files!!

To upgrade your system, follow the software update process. Information here.

The upgrade will install the new KerOS firmware with some consequences on the data:

• Updates stock restore version with liveburner package version.
• Resets the default password on your gateway.
• Erases the whole partition to reinstall the firmware.

To upgrade your system, follow the software update process. Information here.

During an upgrade, the only way to keep system files (network configuration, password…) is to make a backup during the upgrade. This is done by the sysupgrade mechanism.

This mecanism is divided in 2 elements:

• /etc/sysupgrade.conf: Contains the system (KerOS) elements to backup/restore in case of upgrade.
• /etc/sysupgrade.d/: a directory with .conf files where additional elements to backup/restore can be added (i.e. by additional packages).

By default, the system has a predefined list of configuration files to preserve:

File to download - /etc/sysupgrade.conf

If a specific software also needs to keep configurations between upgrades, it is possible to add a .conf file in the /etc/sysupgrade.d directory:

File to download - /etc/sysupgrade.d/myapp.conf

A specific reporting file is generated when an upgrade is done: /user/.sysupgrade.log.

Hotfix packages are only available for a specific version of the firmware. So in case of upgrade, they will be automatically removed. More information on hotfix package here.