I am running into a strange occurrence running RHEL5.1 with an updated policy (2.4.6-106.el5_1.3). By default, it runs the targeted policy. I install the mls and the strict policy and touch /.autorelabel. The first time that I boot to one of these other policies, I get a kernel panic, and I have to use enforcing=0. The strange thing is that I can then go back and forth between any policy without setting permissive mode--that is, I only have to set enforcing=0 the first time that I make a policy change, but subsequent times it is not required. Does fixfiles change something the first time that allows the relabel to work subsequent times in enforcing mode? Any thoughts? Thanks, Forrest
Attachment:
signature.asc
Description: This is a digitally signed message part