Notification would have been nice, but it would be even better if we didn't have to modify this file at all.  Long term, that will be possible through the use of this dual SD device, but I think there are good possibilities for a short term solution.  We don't have to deal with this sort of thing on ubuntu because ubuntu allows us to use named partitions.  I was really hoping that android wouldn't still be using hardcoded partitions after all this time. Is there really nothing that can be done there? I suspect its not just lava that this causes trouble with.  The other possibility for a near term solution which I think we should do regardless of whether the hard coded partitions are fixed, is this idea I discussed recently about having a very slim initramfs based master image that can boot completely. Off of the shared boot / testboot partition. This would mean that we no longer have to make any changes to the mounts in android, and would simultaneously solve Zygmunt's issue with corruption on hard reboots.

Thanks,
Paul Larson