We usually flash a <code>boot.img</code> file (which is the kernel + initramfs) to Android's <code>boot</code> partition (see also: [[deviceinfo_flash_methods]]) - because that is what works and what all other ROMs do. Now the interesting part is the system partition, where we flash our installation image. But the installation image already has a partition layout and own partitions! So you will have ''subpartitions''. In the end, it will look like this:
<pre class="shell">systemp1 # pmOS boot partition, only initramfs-extra gets used from there
The <code>userdata</code> partition is not used yet (proposal to do that is in [https://github.com/postmarketOS/pmbootstrap/issues/60 #60]). But as we are pretty flexible, you can also flash pmOS to the <code>userdata</code> partition, if it has more space and you can't fit it on the <code>system</code> partition. The initramfs will detect it anyway. Just make sure, that you don't have it flashed to ''both'' partitions!<br />
To flash to the <code>userdata</code> partition instead of the <code>system</code> partition,
you currently need to change the config [https://github.com/postmarketOS/pmbootstrap/ blob/6a129669a389446bdbbb2bf6e8576043bc80bf29/pmb/config/__init__.py#L250 here].
=== Future ideas ===