So, to summarize my understanding what should happen (sorry, I'm still quite new to that touch layout, so I rather make sure):
* livecd-rootfs creates /etc/writable/ (use a generic name as we might need it for other cases, and please no dotfiles)
* livecd-rootfs moves /etc/localtime to /etc/writable/localtime and adds a corresponding symlink
* lxc-android-config declares /etc/writable as writable -> this would create a mount point, and hide the original contents of /etc/writable/ as created by livecd-rootfs; how does the mounted file system get /etc/writable/zoneinfo? Is that done magically by the "transition" flag in /etc/system-image/writable-paths?
* timedated and tzdata's postinst check if /etc/localtime point to /etc/writable (i. e. not to /usr/share/zoneinfo) and do its operation on the symlink target instead as a fallback.
So, to summarize my understanding what should happen (sorry, I'm still quite new to that touch layout, so I rather make sure):
* livecd-rootfs creates /etc/writable/ (use a generic name as we might need it for other cases, and please no dotfiles) localtime and adds a corresponding symlink zoneinfo? Is that done magically by the "transition" flag in /etc/system- image/writable- paths? zoneinfo) and do its operation on the symlink target instead as a fallback.
* livecd-rootfs moves /etc/localtime to /etc/writable/
* lxc-android-config declares /etc/writable as writable -> this would create a mount point, and hide the original contents of /etc/writable/ as created by livecd-rootfs; how does the mounted file system get /etc/writable/
* timedated and tzdata's postinst check if /etc/localtime point to /etc/writable (i. e. not to /usr/share/