On 4 June 2014 20:26, Jani Monoses <[email protected]> wrote: > Due to it being called system.img when it was actually flashed to the > Android system partition, the Ubuntu root filesystem image residing under > /data/system.img can be easily confused with the Android system.img that is > under /var/lib/lxc/android/system.img _inside_ the Ubuntu system.img. > > How about moving away and calling the Ubuntu image ubuntu.img ? > Here's a patch to the system-image-upgrader script > > https://code-review.phablet.ubuntu.com/#/c/252/ > > and one to the initramfs script > > https://code.launchpad.net/~jani/ubuntu/utopic/initramfs-tools-ubuntu-touch/image-name/+merge/222091 > > They both preserve working with system.img by hardlinking the two names to > the same file, but prefer ubuntu.img when creating a new image or mounting > one. > > thoughts? > Jani
The other ongoing plan is to get rid of loop-mounting image files, and instead have them on separate partitions. Such that "ubuntu.img" is actually just a normal, e.g. GPT partition with a label UBUNTU, and /var/lib/lxc/android/system.img is also a normal partition. I do agree that mounting a system.img from a system.img file can get rather confusing, very fast. And it did give me a very "Huh?!" moment first time I've discovered this for myself. -- Regards, Dimitri. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
