After much trial and error, I found my error. Or I think what the problem was. In: /etc/sysconfig/selinux I was careless changing: SELINUXTYPE=targeted to SELINUXTYPE=enforcing Oops. Perhaps the wiki can make it clear that what you are to change is: SELINUX=permissive to enforcing... thank you On to the next step! On 12/23/2016 09:58 AM, Fabian Arrotin wrote: > On 23/12/16 02:49, Robert Moskowitz wrote: >> This is on a Cubieboard2 with the OS on a sata HD: >> >> I followed the instructions on the wiki >> >> vi /etc/sysconfig/selinux <- change from "permissive" to "enforcing" >> vi /boot/extlinux/extlinux.conf <- change the "enforce=0" to "enforce=1" >> touch /.autorelabel >> >> I then rebooted and the following appears on the console log: >> >> [ OK ] Reached target Switch Root. >> Starting Switch Root... >> [ 10.682159] systemd-journald[129]: Received SIGTERM from PID 1 >> (systemd). >> [ 11.306507] systemd[1]: Failed to load SELinux policy. >> [!!!!!!] Failed to load SELinux policy, freezing. >> >> >> Note that /boot is sda1 and / is sda3 >> >> I am awaiting guidance. >> >> thank you >> > Hmm, the way I do it is : > - ensure enforce=1 in extlinux.conf (but keep /etc/sysconfig/selinux to > permissive) > - touch /.autorelabel && systemc reboot > > Than wait and when it's finally online, "setenforce 1" and then > /etc/sysconfig/selinux to enforcing > > > > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/arm-dev/attachments/20161226/8359245f/attachment-0006.html>