-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Today when i wanted to uninstall selinux-policy in rawhide i noticed that systemd requires selinux-policy.
I have not tested that thoroughly but could it be that rawhide stops working properly if selinux=0?
I did have issues with systemd starting the network but i am not sure whether its related to aforementioned, that maybe the cable was not plugged in properly or that it was because the policy un-install/upgrade went wrong.
But anyway's systemd requiring selinux-policy seems pretty radical.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/14/2011 04:12 PM, Dominick Grift wrote:
Today when i wanted to uninstall selinux-policy in rawhide i noticed that systemd requires selinux-policy.
I have not tested that thoroughly but could it be that rawhide stops working properly if selinux=0?
I did have issues with systemd starting the network but i am not sure whether its related to aforementioned, that maybe the cable was not plugged in properly or that it was because the policy un-install/upgrade went wrong.
But anyway's systemd requiring selinux-policy seems pretty radical.
- -- selinux mailing list selinux@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/selinux
Open a bug with me cc'd. systemd is doing matchpatchcon/restorecon type operations, but these calls should not be called on a disabled machine, so selinux-policy should not be required.
selinux@lists.fedoraproject.org