On Thu, 2008-04-17 at 17:48 +0000, Justin Mattock wrote: > Hello; I have a quick question. When using a macbook pro there is a > tool(radeontool) that I use to lower the gpu power to a low state > causing significant cooling of the system hardware. The problem I run > into is I'm receiving a: libsepol.check_assertion_helper: assertion on > line 9293 violated by allow sysadm_t memory_device_t:chr_file { read > write }; > Whenever trying to write the allow rule into the policy. What would be > the best step to allow this tool? Well, assuming that it actually requires that access, you can override the assertion / neverallow rule by using the proper policy interface instead of a direct allow rule. audit2allow -R will try to match and use interface calls for you, or you can look them up and use the right one manually. dev_read_raw_memory() and dev_write_raw_memory() appear to be the ones in question. Or you can disable assertion checking by putting expand-check=0 in /etc/selinux/semanage.conf. -- Stephen Smalley National Security Agency -- 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.