After updating the Odroid U3 to kernel 4.1-rc2 (see separate post) I encountered more SELinux / Fedora 22 issues..
This time, SELinux tried to enable itself in ‘targeted’ mode on reboot, despite being ‘disabled’ in the config file..
.... [ OK ] Started Tell Plymouth To Write Out Runtime Data. [ OK ] Started Preprocess NFS configuration. *** Warning -- SELinux targeted policy relabel is required. *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives. [ OK ] Started Restore /run/initramfs on shutdown. [ OK ] Started Rebuild Journal Catalog. ......
SELinux on the CuBox had forced a default to ‘permissive’, but the Odroid defaulted to ‘targeted’, which would force a relabel of all files on the system! As I didn’t want this, I aborted the boot process (pulled the power!)
This would appear to be a possible bug in Fedora 22 – but only on certain armv7 systems.. I have updated one of the x86_64 systems to Fedora 22 and rebooted, and SELinux is staying ‘disabled’.. The Raspberry Pi 2 (armv7) has SELinux configured in the kernel, and has been updated to Fedora 22 – and rebooted – but SELinux stays ‘disabled’..
[root@rgpi2 ~]# sestatus SELinux status: disabled
Tried setting the kernel boot commands on the Odroid U3 to disable SELinux by adding ‘selinux=0‘ but this had no effect..
I aborted the boot process again, and (cross-)re-compiled the kernel – on another system – to take out SELinux completely..
With that, the Odroid booted without problems..
Robert Gadsdon. May 6, 2015.