On 08/08/2013 02:24 PM, Daniel Mirsky wrote:
> I don't remember when I pulled down this set of source, but it was over a 
> week ago. However, I may have pulled down a branch recently, so I will give 
> that a try. I did make sure to set HAVE_SELINUX=true.
> I think the problem is in my init.rc - looks like it was overwritten by TI's 
> board specific init.rc and the problems are coming from there. I will try to 
> merge the two and see what changes.

Ok, that would explain why you didn't transition out of the kernel
domain into the init domain, as there is an explicit setcon command in
the init.rc file.

However, the lack of labeling on /system isn't explained by that
difference.  What kind of filesystem is used for /system - ext4 or
yaffs2 or something else?  We have modified make_ext4fs and
mkyaffs2image to label the system image when it is generated and
adjusted build to invoke them with the file_contexts configuration that
specifies how to label the files.  If you are using some other
filesystem type or are generating the images in a different way, then
they wouldn't get labeled.




--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe seandroid-list" without quotes as the message.

Reply via email to