my main problem with this approach is that i can edit files under /writable/system-data/os/ubuntu-core.sideload/${snappy_os}/* at any time so there isn't actually a readonly / after all (and i think the bind mount would even immediately reflect the changes i made in the writable source dir)
either use an img file that we ship and loop mount from /writable/system-data/os/ubuntu-core.sideload/${snappy_os}/a-rootfs.img|b-rootfs.img or move it to /system-boot/a/rootfs.img and /system-boot/b/rootfs.img (the latter would really be my preferred approach so that you can just re-format /writable to go back to a factory state and/or even make the u-d-f image smaller by simply having a 1byte writable partition created from u-d-f that we grow on first boot. this would also make any kind of installer setup easier)
my main problem with this approach is that i can edit files under /writable/ system- data/os/ ubuntu- core.sideload/ ${snappy_ os}/* at any time so there isn't actually a readonly / after all (and i think the bind mount would even immediately reflect the changes i made in the writable source dir)
either use an img file that we ship and loop mount from /writable/ system- data/os/ ubuntu- core.sideload/ ${snappy_ os}/a-rootfs. img|b-rootfs. img or move it to /system- boot/a/ rootfs. img and /system- boot/b/ rootfs. img (the latter would really be my preferred approach so that you can just re-format /writable to go back to a factory state and/or even make the u-d-f image smaller by simply having a 1byte writable partition created from u-d-f that we grow on first boot. this would also make any kind of installer setup easier)