Why disable SELinux?
It does not provide any significant value for my Raspberry Pi computer
intended for use as an embedded system or in a DACS role, where network
security is important but a simple (root or user) local privilege scheme
is fine. The goals of SELinux are important, but its rocky history
suggests there will continue to be problems. I am reluctant to spend
resources on SELinux for these Raspberry Pi systems, but will do so for
open or multi-user systems.
Actually, the fedora-arm-image-installer "--selinux=off" option
configures SELinux to permissive mode, therefore it will still report
troubles but not interrupt programs because of them. This seems a good
When in the boot process? Was it the grub2 menu
Possibly. I do not know. If you think it useful, I will repeat the
experiment and make a video recording of the console. I do not see
evidence of the pause in the log files:
So why not just use the minimal image?
I probobly ought to, but in this case I wanted to try an aarch64 image
similar to one that Tomáš Frolík reported caused him difficulty.
I've had reports of this [on board wired Ethernet port] working
From the log file, it appears to fail (repeatedly) during appempts to
perform a DHCP operation for its default configuration. However, default
configuration of the USB Ethernet dongle uses DHCP without any problem.
This suggests a hardware setup or driver issue is the culprit.