This reverts commit d2d1a7ffb1.
Revert "selinuxrelabel: Remove attempts to relabel /system"
This reverts commit cae5f24530.
Revert "Recheck /data for selinux labeling"
This reverts commit c4dcb16ca9.
Revert "selinuxrelabel: Add a check for dalvik-cache"
This reverts commit c7e9230614.
Revert "selinuxrelabel: Need to check in priv-app now"
This reverts commit 3013c99acb.
Revert "selinux: When adding userdata labels, do cache too"
This reverts commit 8994907baf.
Revert "selinux: Use a more reliable sentinel to flag /data labelling"
This reverts commit b52874de53.
Change-Id: I7779aaca3b0751ed74d525292681817182a0aa7f
These are a no-op due to the additional block-device protection from
e18c0d508a
so get rid of them entirely. Any installing recovery (or equivalent
installation process) should handle the labeling of system components
on its own.
Change-Id: I14c50f08efa6f05b03fad4fbc404219cc504e1ff
TBD: Do we still want to label unlabeled files?
This simply adds checks for selinux labels for
files under /data/misc/wifi which were not labeled
correctly for some devices
Change-Id: Iaacf6db792aaea1485502b424d639a1212c5841b
Since not all recoveries out there will support the OTA packages'
own labeling, check at boot if the system needs labels (and
apply them)
Change-Id: I58767977b90a78a12efe7bd9d713654eadf47e7a
"getprop" depends on the presence of the property workspace
env var, which is created by the first starting service. Why
not make that sysinit itself? (\/) (°,,,°) (\/)
Allow user to provide userinit.sh and/or userinit.d/*
scripts under /data/local to be run on each boot.
Change-Id: I96f3034bcdea8d4cc75929d21b69efa31c1cb108
increase required space needed for market downloads from ~20MB
to ~60MB (~105MB if system dalvik is on /cache)
Change-Id: I52fcd648374db4bf73ff478e9991a6a3162521d5
this is useful for all user which want to use cMTD or static
partition size (like alpharev) to assign more space to /data
reducing /cache size
Change-Id: Ib251c9bea1dea50b6c444df977aa605e58008c41
Removed label requirement, cause too many trouble on user
The 2nd SD Card partition will be mounted as sd-ext with ext3fs
(there are some problem with ext4, we stay on 3 until 4 problem
will be sorted)
Change-Id: I87e53d1714d84fbdafeb80599ebb3e62b3a24b1e
check for mmc device type = SD
mount sd-ext partition by label = sd-ext
we are smart, so only ext4 support
removed wait for device
Change-Id: Ie1ee2de3365d5515030d46801099418607e1265e
Wolfgang Wiedmeyer