On Fri, Dec 27, 2013 at 7:54 PM, sri linux <[email protected]> wrote:

> I tried "restorecon" from init.rc file, which doesn't have any affect.
> Also, I tried with an allow rule to allow relabelto, with this I can't
> build as there is a neverallow rule for this.
>
>
>
> On Fri, Dec 27, 2013 at 4:05 PM, sri linux <[email protected]> wrote:
>
>> Dear Experts,
>>
>> I have a file in one of the partition, for which, I see below as a
>> default context:
>> -rw-rw-r-- system   root              u:object_r:unlabeled:s0 file_xyz
>>
>> I tried to change the context using type_transition, which doesn't seem
>> to be working - I still see unlabeled in the context.
>>
>> Can someone suggest the best way to change the context of the file which
>> is unlabeled?
>>
>
What does 'restorecon -nv file_xyz' say? That should show a valid type for
your policy. Do you have the filesystem mounted read only? If so you won't
be able to change the label. If you replaced the stock policy for your
device with a custom one and didn't replace it with your own file context
file and relabel everything it's possible you could have some files that
have types only valid in the stock policy and not valid in yours.



>
>>
>>
>
> _______________________________________________
> Seandroid-list mailing list
> [email protected]
> To unsubscribe, send email to [email protected].
> To get help, send an email containing "help" to
> [email protected].
>
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to 
[email protected].

Reply via email to