policy-1.9.2-9 causes kernel panic during boot

[Fred New]

5. aprill 2004. a. 13:40, Jim Tate wrote:
> 
> J. Scott Farrow wrote:
> 
> >On Sun, 2004-04-04 at 11:27, Fred New wrote:
> >  
> >
> >>In my FC2T2 system, I upgraded from policy-1.9.2-5 to policy-1.9.2-9
> >>and ended up with (as I recall) the following files in
> >>/etc/security/selinux:
> >>
> >>file_contexts
> >>file_contexts.rpmnew
> >>policy.
> >>pllicy.16.rpmsave
> >>
<snip>
> Your right about the /etc/security/selinux/policy.16 file, I
> uninstalled policy-1.9.2-9 and reinstalled policy and the policy.16
> file is not being properly created, all that is there is file with
> a big ? in it. Even if i do a rpm -ivh --force, I still get the
> same error message as shown below, but the directory path and
> uncreated file is there. The line number 1131-1758 I edited in,
> that is the the number of lines that show in error message
> 
> /etc/security/selinux/file_contexts:  invalid context 
> system_u:object_r:amanda_recover_dir_t on line number 1131-1758
> Preparing... ########################################### [100%]
>   1:policy   ########################################### [100%]
> Can't open '/etc/security/selinux/policy.16':  No such file 
> or directory
> error: %post(policy-1.9.2-9) scriptlet failed, exit status 2
> 
> I have my /etc/sysconfig/selinux file set to 
> SELINUX=permissive , that is the only way
> I can get in without bootup locking up with Kernel Panic!!
> 
> Jim Taate

I installed policy-1.9.2-9 again and got the same files as above. This
time I renamed
     policy. -> policy.16
     file_contexts        -> file_contexts.rpmold
     file_contexts.rpmnew -> file_contexts
and the following reboot was successful.  I might have had to do a
fixfiles relabel, too.

And this morning I have read that I might have been able to get around
the policy load failure (and kernel panic) by specifying
     init=/bin/bash
in the kernel boot parms.  I haven't tried it, but this could have
permitted me to recover enough to rename the policy. file.

Fred "still in enforcing mode" New