Jump to navigation Jump to search
59 bytes removed ,  21:13, 7 May 2020
Update links
<pre class="shell">systemp1 # pmOS boot partition, only initramfs-extra gets used from there
systemp2 # pmOS (un)encrypted root filesystem</pre>
The initramfs (in the <code>boot.img</code> file!) will automatically find and mount the pmOS boot and root partition, load the <code>initramfs-extra</code> (which contains additional files, it was split to save space) and take care of booting through until [[Glossary#openrc OpenRC|OpenRC]] takes over.
==== Flashing to "userdata" ====
{{note|See also: Allow booting from an image file (/data/postmarketOS.img) instead of flashing to a partition ({{github|953}})}}
There might be scenarios, in which the partition type of the <code>system</code> partition can not be changed through the flasher, because it only allows [https://en.{{|YAFFS#YAFFS2 yaffs2] |YAFFS2}} or simg with ext4 support (during research for the mozilla flame, we found that to be the case ({{issue|299}}) - however, it also has an SD slot, so we did not continue this way ({{issue|337}})).
A proposal we have for that case, is to have one big ext4/yaffs partition, and include the whole system image file inside that. Then we would adjust the initramfs code to find the boot and root partitions inside that, and teach it how to resize the whole thing to the maximum partition size. We already did some experiments, and so far everything worked (talk to drebrez or ollieparanoid).
[[Category:Technical Reference]]


Navigation menu