On Fri, Oct 31, 2008 at 4:25 PM, Mark Murphy <[EMAIL PROTECTED]>wrote:
> > Disconnect wrote: > > They are administered through sudo, which is becoming root. > > Or they are administered through a GUI/Web interface. Like you see in > many consumer-grade embedded-Linux environments (TiVo, Linksys routers, > etc.). These things involve root access. > > And there are 2 big use-cases for this: backup/restore and vpn access. > > Android may need hooks to support a third-party backup/restore solution. > That does not imply the need for root access. > > Userspace VPNs (e.g., OpenVPN) exist. > Explain to me how you run openvpn (which modifies network devices and routes) as a normal user. It runs in -userspace- sure, but then again, they all do... That doesn't mean it can run as a -user-. > > > The third, less provider-friendly reason is custom firmware flashing to > > do things like fix the abomination that is 'email'. (Or translate the > > UI. Or fix the scheduler. Or...etc.) > > You don't need root to flash firmware on a Linksys router. > To suborn it into running (eg) openwrt you need to go after either the tftp bootloader or the standard (root) flash method. So again, you need root. (Esp in this case, since tmob is not going to release the keys for image signing to the rest of us.) > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.3 Published! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
