Quote:
Originally Posted by Nyoxi
Do you also have an idea how could we use that? Just by switching mmcblk0p1 from ext3 to squashfs would not help. To make proper use of the free space we would have to create new partition for our overlay between *p1 and *p2 which whould cause renumbering of all the other partitions. And would mean changing lot's of scripts and files on both main and diag partitions, but most importantly you probably wouldn't be able to boot into diags at all (or is there some idme or other variable that sais which partition to use?). The other option is to move all the partitions to move the free space to the end but this has also a few problems. First, are we sure diags will still work? Isn't there anything that relies on the original address of mmcblk0p2 on MMC? And you would have to do that before user puts his data onto userspace or you risk not having enough free space to move the partition.
But maybe I missed something.
By the way, I wouldn't shun people at lab126 because of this -- they didn't decide to use overlay (we did). And simply exchanging the free space on root filesystem for free space on overlay doesn't make you gain anything.
PS: Could you also post the real filesystem usage to be completely fair? I don't have those devices and I am too lazy to check that for KT.  |
The startup logic for both main and diags respect whatever they find for the 4 main primary partitions. The values in mntus.params are only used if the USB drive cannot be mounted successfully.
Because p4 has its own partition table, the USB drive resides in "mmcblk0p4p1", and you have 3 more empty "inner" partitions you can use. You need to either loop mount mmcblk0p4 then mount the second partition inside that (mmcblk0p4p2), or you just loop mount it directly with an offset (like how /mnt/us is sometimes mounted). Of course you need to shrink mmcblk0p4p1 to make room to expand one or more of the empty inner partitions.
