Mender blog

In this post we're going to explore using LVM to reduce the space needed by a dual rootfs setup. In a typical dual rootfs setup, the device needs to have two times the space needed by the rootfs partition, in order to have an inactive partition to stream a new update into. But in a typical patch update, not that much will have changed from what's already on the active partition. Perhaps a few libr...

We are excited to have Boundary Devices LLC, a leading supplier of iMX-based single board computers and System-on-Modules (SoMs), partner with Mender to further accelerate the adoption of over-the-air (OTA) software updates in the connected embedded devices market.

Boundary Devices provides high quality and cost effective boards that include industry-leading software support. Integrating Mend...

Mender 2.6 will be the last on-premise release series to support Mender clients 1.7.0 and older out of the box. It will still be possible to support these clients by performing extra configuration steps, and more details about this will be posted in the announcement for the Mender 2.7 release. However, the recommendation is to upgrade the client to 1.7.1 or newer before upgrading the server to 2.7...

One of the biggest challenges in IoT security is the risk posed with an insecure software update process. Updates are critical for maintaining security on connected devices as the software on these devices will become outdated during their lifetime and vulnerabilities are certain to arise if left in their initial states. Therefore a secure, risk tolerant and efficient update mechanism must be...

We are happy to announce Mender 2.6 release.

Mender 2.6 comes with major architectural improvements to enable support for new use cases in Mender. The first feature to leverage the new architecture is also here: the secure Remote terminal, and more will come in future releases!

From the usage point of view, the new Remote terminal does exactly what you would expect: in...