OpenBMC Image Management

Anton D. Kachalov mouse at
Thu Jan 26 21:43:17 AEDT 2017


26.01.2017, 01:32, "Adriana Kobylak" <anoo at>:
> General:
> * Use CRAMFS for read-only partitions, and UBIFS for read-write partitions.

Why CRAMFS? It's small, but supports only zlib compression, has a 16MB file size limitation and marked as obsolete in kernel tree. Why not SquashFS? It's better for larger projects, has a number of modern compression algos.

> * Ability to ‘patch’ by copying a Hostboot image *.bin into a designated directory (/usr/local/ for example).

Would it be good to add support for opkg-based packaging to incrementally (hotfix) system's update? I use it in OpenWRT.

> * Tool to write from PNOR image to BMC format. Implement UBI initially but it could be extended to support different volume managements on other BMCs.
> BMC:
> *Save multiple firmware versions, starting with 2, to provide the ability to roll-back if needed. If single BMC chip system, save both versions there. If two BMC chip system, save other version in 2nd chip.
> * Implement various levels of ‘persistency’, such as dev, factory, field. Dev persistency would allow for local patches (/usr/local/ for example) that can be cleared before shipping to customers. Factory mode could delete the location where user data such as network settings resides but preserves the mac address and uuid for example. Etc.
> Thanks,
> Adriana
> _______________________________________________
> openbmc mailing list
> openbmc at

Anton D. Kachalov

More information about the openbmc mailing list