rootdir: Change sysfs permissions to allow user control ksm

Change-Id: I8a57a3d3bb7b5cd34d58416ca8778dfd6df3111b
adbd: Disable "adb root" by system property (2/3)

 * Require persist.sys.root_access=1 on non-eng debuggable builds

Change-Id: Iedab030e81ffb525fed64aed80cf0014f3e07073
Allow system to call custom reboot cmd

Change-Id: Id726b46f644e72c9a67d64777abe1e3dbdbc0a82
init: Extend the check for charger mode

In ICS, Google introduced charge mode handling (see http://bit.ly/wfs7ck).
Extend this with check for battchg_pause used in legacy kernels.

Change-Id: Ia8fba16efa2a7d9416e38dd68d4fef84d37aea5e
Merge "rootdir: Change sysfs permissions to allow user control ksm" into ics
set /system/etc/init.d/* permissions

ported from CM7

Change-Id: I279d78679f7d779d6cd6bbc6c834d94706937ae8
Merge "init: Extend the check for charger mode" into ics
run sysinit during boot

ported from CM7

Change-Id: I08f8e23d83ce45366ff2a994d110dd3431efa017
init: Never allow two same-service processes to exist simultaneously.

A stopping service now remains in SVC_RUNNING state until its exiting
process has been reaped by waitpid.  This prevents a "stop, start" sequence
from spawning a second service process before resources held by the first
are released.  However, a "stop, start" pair _will_ restart the service
after exit (unless critical or oneshot).

This scenario was originally special-cased by the SVC_RESTART state used by
the restart command.  However, we have observed instances where services
are, unintentionally, stopped and started "too quickly," and so
simultaneous processes for the same service should never be allowed.  Note
the SVC_RESTART state (and restart) command is still useful to explicitly
restart critical and oneshot services, for which the "stop, start"
procedure is not intended.
init: Don't confuse do_exec with other exiting processes.

The waitpid call in do_exec may return early with EINTR when init receives
a signal, e.g., a SIGCHLD from an exiting service process.  do_exec should
check waitpid for an EINTR "error", to ensure that it returns only after
waiting on its child process.
Toolbox implementation of chown has a bad print

When the chown program fails it prints out an error message
and is describing itself as chmod. This has been corrected.

Change-Id: I2c489975f09343bdf66acbf7df6e7183c2daff78
Signed-off-by: christian bejram <christian.bejram@stericsson.com>
core: allow radio users to access all rmnet* interface

Change-Id: Ibc3bf9654cf68362369422f82afe53ef86e3e710
Modular backuptool.sh.  Executes backup and restore methods defined in arbitrary /system/addon.d/*.sh scripts.

Set permissions on /system/addon.d/ and files within.

Patch Series
============
http://review.cyanogenmod.com/#change,13265
CyanogenMod/android_build
  * edify generator
http://review.cyanogenmod.com/#change,13266
CyanogenMod/android_system_core
  * permissions on /system/addon.d
http://review.cyanogenmod.com/#change,13267
CyanogenMod/android_vendor_cm
  * 50-cm.sh reference backup script
  * modular backuptool.sh
  * support backuptool.functions used by /system/addon.d/*.sh scripts

Change-Id: I4f1464ea8d55f45d47ba760a7a448036a46feb00
Merge "Modular backuptool.sh.  Executes backup and restore methods defined in arbitrary /system/addon.d/*.sh scripts." into ics
audio: Don't use QCOM_HARDWARE when AUDIO_LEGACY is active

The older (GB) blobs used with AUDIO_LEGACY do not support the
new enums.

Change-Id: If80539060dbef53e984ca3d52d65cac6a499e8dd
init: Let radio user manipulate service properties

I'm seeing some devices (with broadcom's btld) in which the
radio services (RIL) use the service. namespace to pass or store
data...

Conflicts:

	init/property_service.c

Change-Id: I6e3177689a12b0925064e615408bc1e0f175bcf3
Merge "adbd: Disable "adb root" by system property (2/3)" into ics
added offline booting by jerryscript and build fixes

Change-Id: I6afb2f6cdbe2cad64b282a6590ed2096f65ef2aa