Hi, > I suppose part of the problem is believing Android should behave > like a unix-like OS.
Erm ... seriously? I mean, yeah, sure, I haven't seen any documentation that specifies explicitly "Android will behave like a unix-like OS", so it might be my mistake to assume so. But then again, you could use that same argument for justifying just about any behaviour. Calling connect() deleted your database files? I suppose part of the problem is believing Android should behave like a unix-like OS! Calling open() caused a core dump of your process to be published on some pastebin? I suppose part of the problem is believing Android should behave like a unix-like OS! I mean, is there any documentation anywhere that specifies what Android actually _is_ if it is _not_ unix-like, or is it essentially undefined and Android is actually one giant random behaviour generator, and if anything resembles the behaviour of a unix, that's purely coincidental and not something to be relied upon? Does the native code interface have any defined semantics, or is it just a pile of undefined stuff that's not good for anything? > Recall that for many revisions of Android there > was not even a native code capability at all, you only had what the > Java SDK gave you. But you do recall that Android nowadays _has_ a native code capability, right? "This feature is new, therefore its behaviour is undefined" does not sound particularly convincing to me. > Nick can probably expand on the rationale but the commit and commit > message is here: > > https://android.googlesource.com/platform/external/sepolicy/+/85ce2c7 Thanks! I have added him to the Cc, to hopefully get his attention (hi there!) ... Regards, Florian _______________________________________________ Seandroid-list mailing list Seandroid-list@tycho.nsa.gov To unsubscribe, send email to seandroid-list-le...@tycho.nsa.gov. To get help, send an email containing "help" to seandroid-list-requ...@tycho.nsa.gov.
