In the pre-ubifs days it was common practice in embedded systems to setup several (MTD) partitions in flash for protection. For example, a partition containing a read-only file system could be mounted as /, with a separate writeable partition for configuration data mounted as /home or /data or whatever.
On the other hand, one of the main features of UBI is that it provides logical "UBI volumes" while at the same time doing wear-leveling across the whole flash device. Quoting from the MTD website:
UBI implements wear-leveling across whole flash device (i.e., you may continuously write/erase only one logical eraseblock of an UBI volume, but UBI will spread this to all physical eraseblocks of the flash chip);
My question is: Does it make sense to have separate UBI volumes for, e.g. a read only file system vs configuration data? Or is this pointless due to the fact that the whole flash participates in wear-leveling internally?