| 1 |
Yes, there are problems in the SELinux code in ls that I am |
| 2 |
investigating. I does not have to do with the policy. If you don't |
| 3 |
load the policy, as you're suggesting, then SELinux is disabled, and |
| 4 |
none of the SELinux code in ls (or any SELinux-patched program) is used. |
| 5 |
|
| 6 |
On Tue, 2003-11-18 at 04:47, Tiago Lima wrote: |
| 7 |
> I suspect its from the "policy" (whether the rules or the use of the |
| 8 |
> policy itself)... because If I remove the initrd.gz from boot "ls" |
| 9 |
> works fine but the packages don't (because of the file contexts)... |
| 10 |
> ----- Original Message ----- |
| 11 |
> From: Miguel Sousa Filipe |
| 12 |
> In the end I did a emerge world -e, in the emerge of perl, the |
| 13 |
> emerge stops with |
| 14 |
> a "endeless loop" in a test, while "ls" is using 99% cpu. |
| 15 |
> It never stops.... |
| 16 |
-- |
| 17 |
Chris PeBenito |
| 18 |
<pebenito@g.o> |
| 19 |
Developer, |
| 20 |
Hardened Gentoo Linux |
| 21 |
Embedded Gentoo Linux |
| 22 |
|
| 23 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
| 24 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |
Archives