| 1 |
Matt Harrison wrote: |
| 2 |
> On Sun, Oct 26, 2008 at 03:32:10PM -0400, Mike Edenfield wrote: |
| 3 |
>> Matt Harrison wrote: |
| 4 |
>> |
| 5 |
>>> The problem is that even though the selinux USE flag isn't exabled, |
| 6 |
>>> packages |
| 7 |
>>> like coreutils are still linking into libselinux. So if I remove |
| 8 |
>>> libselinux |
| 9 |
>>> and all the selinux related packages, it breaks a whole load of binaries |
| 10 |
>>> on |
| 11 |
>>> the system, so much so that I can't recompile packages afterwards. |
| 12 |
>> Once you switch to a non-SELinux profile you still need to rebuild the |
| 13 |
>> packages that used the library. Building them without the selinux USE flag |
| 14 |
>> will prevent them from linking to the library. Once they're all rebuilt, |
| 15 |
>> then you can remove the SELinux userland stuff. |
| 16 |
> |
| 17 |
> But I've already rebuilt the packages, like coreutils, yet ldd on /bin/mv |
| 18 |
> still shows libselinux linked in. |
| 19 |
|
| 20 |
revdep-rebuild won't do you any good as long as coreutils automagically |
| 21 |
links against libselinux. |
| 22 |
|
| 23 |
This has been fixed in coreutils-6.10-r3 and coreutils-6.12-r2, so I |
| 24 |
suggest using one of these versions. |
| 25 |
|
| 26 |
|
| 27 |
Regards, |
| 28 |
Andi |
Archives