Thread: [Under consideration] More efficient and flexible use of internal flash
View Single Post
titan is offline titan
2010-01-12 , 19:58
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#50
Originally Posted by Graham Cobb View Post
In my view, the main issue is not whether users need this repartitioning but whether applications which people develop need it.
ok, assuming that "storing my files" is also an application
I agree with Fanoush that we need the system to be able to have part of the MMC which it owns and which can be over-written during upgrades. This could be mounted as /home (or, maybe, something like /home/system).
For those of us who need to be able to boot different software releases, for testing, we would want to have different /home's available, which we arrange to be mounted correctly for the image we are booting (a task for the bootmenu).
I think there should be as few as possible partitions as you cannot use the free space on other partitions - which would be wasted if you choose an inappropriate partition schema.

I think the cleanest solution would be:
/emmc - single ext3 partitions on the eMMC mounted on /emmc
/emmc/opt - directory for addons managed by system
/emmc/home - user directories
/emmc/loopback/ - directory for loopback file incl. MyDocs FAT file
If you really want to boot multiple systems you could create an appropriate
symlink to opt.<version> during boot.

loopback files can be easily resized online without dangerous repartitioning
and you could keep multiple FAT images or, e.g. NTFS images.