Provide an upgrade path between images

[dm8tbr]

I guess using something like the home.img we had on gen6 would be the easiest. In this case it would probably divide like in the Archos firmware and /data would end up in the common image.

We could call it data.img and maybe stuff it in some place like System so that the user doesn't go out and delete it?

This is free for takers! Patches/proof of concept/tests very much appreciated!

[furies]

I think the data.img should be nice, we should try to load it but without permission for global user (e.g "chmod 770" or in the same idea).

[dm8tbr]

I guess this is still valid?

[divx118]

Changed component so it will show up on ticket page CM

[illifant]

Any reason why we can't just mount -bind /mnt_data/.CM_data /data or even use a symlink? I see only foolproof issues.

[divx118]

@illifant:I thought about your idea.
However I see some issues:
- gapps, because they are in /system/apps (Not a major issue IMO)
- on gen8 /mnt/storage (internal storage) can be and is by most users formatted fat and not ext3.

[anonymous]

You're right, filesystem shouldn't be fat. I haven't thought of this.

[divx118]

We could write an update script that would start on first boot and copy over the data folder and gapps in /system/apps