Dominik J. Fischer wrote:
Obviously, the SELinux base policy even does not provide rules for those
devices initialized at bootup.
Assuming these are *only* happening when you first boot up,
and don't continue to happen, these errors are mostly harmless.
They are happening during the boot process, prior to having
udev up and the /dev partition populated correctly. Before
that, your /dev nodes are mislabeled, so the boot scripts
attempts to write to /dev/console, /dev/null, etc. are
generating errors. The only device *needed* for Gentoo to
boot before udev is running is /dev/null, which you can fix
by doing this:
# mkdir /mnt/fakeroot
# mount -o bind / /fakeroot
# cd /fakeroot/dev
# setfiles -r /fakeroot \
/etc/selinux/strict/contexts/files/file_contexts \
.
# cd /
# umount /fakeroot
You will probably still get a few audit messages (about
/dev/console) but its nothing that is required for Gentoo to
boot.
--Mike
