On Fri, Nov 9, 2012 at 5:26 PM, Shuiqing Wang <s.wang@xxxxxxxxxxxxxxx> wrote: > I am new to SEAndroid and I have a couple of questions about reloading > policy, on Android 4.0.4. > > 1. I read from the SEAndroid wiki that I can copy a new policy file > to /data/system, and issue a "setprop selinux.reload_policy 1" command > in adb shell to trigger a reload of policy. I did this but nothing > happened. How do I know the reload is successful or not? I checked dmesg > but saw nothing useful. > > 2. How to I know which policy file is pointed to by the kernel currently > if multiple policies exist on my device? Is there a adb shell command or > log file that can help? Questions about SE Android should be directed to the seandroid-list these days; see the wiki for how to subscribe. Assuming that you have in fact built with SE Android enabled, then you should have output in dmesg about the policy load and which policy file was loaded. Any particular reason you are using 4.0.4 rather than 4.1.2 or master? -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
