System updates

JelinaOS updates cover the system, kernel, device agent, and incremental updates through cloud and local channels. With A/B systems, every update has a recovery path.

Update targets

Target	Description
System (JelinaOS)	System version upgrades with new features and security fixes
Kernel	Kernel updates for performance and hardware support improvements
Device agent	Device management component updates
Incremental updates	Incremental system patches for rapid deployment

Update methods

Cloud OTA (recommended)

With JelinaCloud connected, manage updates centrally through fleet or device pages:

1. Specify the target system, kernel, or agent version in the cloud.
2. The cloud delivers updates according to policy, supporting pinned versions and staged execution.
3. Devices automatically download and apply updates, with status visible in real time in the cloud.

Cloud updates also support offline update packages. Download packages for devices without connectivity and apply them on site. Packages can also be delivered on removable media such as USB drives; devices process updates automatically when the medium is connected.

Local OTA

Without a cloud environment, use the device-side update tool:

# View version and update status
jelina-local-ota -g
jelina-local-ota -s
jelina-local-ota --json --status      # Structured status output

# View updates awaiting approval in local-confirmation mode
jelina-local-ota --confirmation

# Precheck the update package: parse and verify without submitting
jelina-local-ota --check <update-package>

Once verified, submit the update package for application. If confirmation is enabled, the update remains pending until confirmed:

jelina-local-ota <update-package>
jelina-local-ota -c -w    # Confirm the pending update and follow its progress

Single-component packages (.pkg)

Use the installer to apply individual component packages, such as device agent or application components:

jelina-instpackage --pkg-info <component-package.pkg>   # View package information without installing
jelina-instpackage <component-package.pkg>              # Install a component package

Verify the package source and checksum before installation. Some component updates require a reboot to take effect.

Update package types

JelinaOS uses two update package formats with different purposes and entry points:

Package type	Format	Purpose	Installation entry point
Single-component package	.pkg	Update one component, such as the system, kernel, device agent, or application component	jelina-instpackage
OTA update package	.zip	Complete update containing target state and multiple components, centrally orchestrated by the device agent	jelina-local-ota

Installation methods

Single-component packages use different installation methods depending on the target:

Method	Description
Full write	Write to a target partition, commonly the standby A/B partition
Extraction	Extract to a specified partition, file, or directory
Incremental installation	Install as an overlay—an incremental update without partition switching
Executable installation	Install and execute once; high risk, for specific scenarios only

Successful installation does not mean activation

Installer success does not mean that new content is active. Components such as the system and kernel require a reboot or remount after updating. After rebooting, verify the actual running version and partition before considering the update complete.

Do not interchange the two package types

• Do not pass OTA packages (.zip) to the single-component installer or manually install component packages (.pkg) while bypassing target state; doing so disrupts component update ordering.
• Apply offline OTA packages downloaded from the cloud through jelina-local-ota.

Update confirmation

At critical sites, configure updates to execute after local confirmation:

• New versions from the cloud are stored on the device without immediate installation.
• Updates begin only after on-site personnel confirm.
• Confirmation can use device-side commands or the device interface.
• Until confirmation, the device continues running the current version, leaving the final decision on site.

Update workflow and protection

Download update → Verify integrity → Write standby partition → Reboot and switch → Boot verification
                                                                                          │
                                                                              ✅ Pass: continue running
                                                                              ❌ Fail: roll back automatically

• No business interruption during update preparation: Downloads and writes occur in the background while the device continues running.
• Automatic rollback on failure: Failed validation after switching restores the original system.
• Version rollback: If a newly applied version has problems, return to the previous version.

View update status

jelina-info          # View current version and boot partition
jelina-local-ota -s  # View update status and pending updates

The cloud device dashboard also displays versions and update status.

Update recommendations

Scenario	Recommendation
Routine maintenance	Apply patches promptly to maintain the security baseline
Version upgrades	Validate on test devices before batch deployment
Industries with strict compliance requirements	Enable local confirmation and validate thoroughly before updates
Sites with limited bandwidth	Use incremental updates or offline packages

Related documentation

• Updates and disaster recovery — Update principles and protection
• Cloud application deployment and OTA — Cloud update operations
• A/B systems and switching — Partition switching and rollback