I'm told you would be able to assist with our selinux issue with ARM arch?
Here is an fpaste of the bootup:
One of the ill effects is that NetworkManager.service does not work during the boot sequence. Afterward NM works with a restart, so perhaps some context is wrong, or some race condition. Jon Masters was speculating that perhaps the way systemd starts things with the wrong context on the service, or something similar.
The environment is a pandaboard ES (omap 3.6 kernel) running F18 alpha.
Hopefully the above paste will provide a clue that help get us going in the right direction.
If you desire we can provide you access to a pandaboard if that would be helpful?
Any attention you can spare for this would be very appreciated!
Thanks in advance
-Jon Disnard
irc: masta
fas: parasense
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
