When starting the current (20070419) LiveCD, a lot of messages saying (e.g.)
/var/lib/random-seed: no dev
appear on the console after readahead starts.
Happens on regular installs too.
I've commented out the fprintf so that it's at least not as annoying, but could
use looking to see why it's happening still. But now just a release blocker and
not a test release blocker
The problem is selinux. I can't reproduce it with selinux=0. The readahead needs
to read /dev/root (and others partitions where are files from readahead lists).
open("/dev/root", O_RDONLY) = -1 EACCES (Permission denied)
Note: the readahead runs (on FC6) with system_u:system_r:readahead_t:s0
It seems the problem is pretty old (include FC6). Now it appears, because the
new version doesn't ignore the problem and reports it to stderr.
It's important fix the problem in selinux policy, because it has terrible impact
to readahead performace -- now (with selinux) the readahead can't read
information about FS blocks.
I don't know why, but I cannot found any avc messages about this issue in system
Created attachment 153279 [details]
Please try this policy file to see if it fixes the problem
Steps to build
Extract myreadahead.te to a local file, as root execute the following
# yum install selinux-policy-devel
# make -f /usr/share/selinux/devel/Makefile
# semodule myreadahead.pp
See if readahead works better.
It works for me. Please, submit the change to standard system policy. Thanks.
Already in selinux-policy-2.6.1-1.fc7
This okay to me now