LVM support, CRYPTROOT and current implementation.
Description
I am in the process of adding `LVM` support to Armbian. It 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`.
I am in the process of adding `LVM` support to Armbian. It 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`.