On Sat, May 26, 2012 at 12:47 PM, Mark Murphy <[email protected]> wrote: > On Sat, May 26, 2012 at 3:42 AM, Latimerius <[email protected]> wrote: > > External storage classically was on vfat (e.g., SD card), where Linux > permissions really don't work too well. Internal storage is where the > full power of the Linux permission model can be applied (YAFFS2 and, > now, ext4).
Ah, so it's motivated mostly by implementation concerns. Fair enough. > Resources are world-readable to allow things like the home screen to > work (tough to render launcher icons if you cannot access the > drawables and captions). > > That being said, when I made the discovery you did, I too was > surprised. I have now made it through the "seven stages of WTF?" and > am now on "acceptance". :-) What else can we do? :-) I suppose it could have been done by identifying "platform-facing" resources/assets and putting those into a publicly accessible location while leaving the rest private, or at least assets/ could have been made private as no standard stuff goes there AFAIK... but oh well. Although... I don't think it's possible to set up an APK so that some files go straight into the private internal storage area during installation, is it? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
