LVM support, CRYPTROOT and current implementation.

[rvalle]

Which feature would you like to have?

I am in the process of adding LVM support to Armbian, unfortunately this can not be implmented from an extension.

LVM support is essentially similar to CRYPTROOT. However CRYPTROOT support is hardcoded into the partitioning image functions.

In my opinion, both CRYPTROOT and LVM, take the designated root partition, perform some custom actions, and choose a custom rootdevice.

I think it should be ideal to move CRYPTROOT to an optional extension, and then use the same framework to implement LVM support.

I think the easiest way to do his, is allowing the post_create_partitions hook to optionally pick the rootdevice.

Funding

• I am willing to cover expenses

[github-actions]

Jira ticket: AR-2032

[viraniac]

Yes, some parts are hardcoded, while others were moved to a separate extension. As you already mentioned that you are working on lvm support, probably you can move the rest to the existing extension and create an extension for LVM as well. Feel free to raise a PR with the same.