Hans de Goede wrote:
It is really not that bad, as long as you learn: -system does poof -don't panic most likely selinux * -reboot with selinux=disabled -try again after a few days without selinux=disabled
It's really that bad.If you're running half the time with selinux disabled, how are you supposed to trace when/how individual selinux problems are fixed/introduced ?
-- Nicolas Mailhot