Hi, On Wednesday, June 3, 2009 9:20:21 PM UTC+2, JoelV wrote: > > In porting Android to a new device, I've run into some use cases where > we've added support for some native OEM hal-specific services and > hardware resources which do not seem to fall within the scope of the > existing ID's defined in system/core/include/private/ > I think I am in need of the same kind of stuff. None of the available groups really fits my purpose. What other alternative exists?
-Running processes as root/system and using normal android permissions/process separation? more stuff? android_filesystem_config.h. In order to execute these services at the > appropriate privilege level, and provide controlled access to certain > shared resources, I'd like to define a few new OEM specific user/group > ID's. Are there guidelines for OEM's to extend these ID's? Should they > be in a specific range (for example, can we allocate the 9000-9100 > range for OEM's) and include an OEM prefix so they don't conflict with > any new ID's that may be added in future Android releases? > > Thanks, > Joel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
