On Tue, 2005-06-28 at 13:46 -0400, Chuck Anderson wrote:
I updated the bz ticket #161867. All the systems I had this problem
with were running 2.6.11-1.27_FC3 at the time the update was done.
The systems running 2.6.11-1.35_FC3 didn't experience the problem. So
it does appear that the problem is the older kernel and the newer
policy.
Hmmm...interesting, since AFAIK, the SELinux code didn't change between
those two kernels, and FC3 kernel has no SELinux-related patches in it
(it just uses the upstream code). Side effect of another patch in the
FC3 kernel?
--
Stephen Smalley
National Security Agency