| |||||||||||||
Android, forking, and controlAndroid, forking, and controlPosted Jun 7, 2011 13:53 UTC (Tue) by karim (subscriber, #114)In reply to: Android, forking, and control by swetland Parent article: Android, forking, and control
Thanks for this nugget. Very insightful.
Totally agree on the "be they real or imagined"part. The downside of that, though, is that a lot of "standard" packages and modus operandi were thrown out the window (Busybox, uClibc, ...) I mean no offense, but Toolbox is nowhere near Busybox in terms of capabilities. In fact, the first thing I do when starting work on an AOSP tree is get Busybox in there ... Nothing major really, but an annoyance still.
(Log in to post comments)
Android, forking, and control Posted Jun 7, 2011 15:49 UTC (Tue) by swetland (subscriber, #63414) [Link]
No offense taken. Toolbox was never intended to be a full-featured environment, simply some minimal tools for debugging. The reason /data/local is writeable by the "shell" user is that the expectation was that you'd throw whatever commandline goodies you want in /data/local/{bin,lib,etc}.
|
|||||||||||||