policy and policy-source

[Richard Hally]

Olu Akins wrote:

> While trying to upgrade policy and policy-source, I received these errors
>
> 4:policy                 ########################################### [ 
> 24%]
> warning: /etc/security/selinux/policy.16 created as
> /etc/security/selinux/policy.16.rpmnew
> cat: /selinux/policyvers: No such file or directory
> /usr/sbin/load_policy:  security_load_policy failed
> error: %post(policy-1.9.2-12) scriptlet failed, exit status 3
>   5:policy-sources         ########################################### 
> [ 29%]
> make: Entering directory `/etc/security/selinux/src/policy'
> mkdir -p /etc/security/selinux
> /usr/bin/checkpolicy -c -o /etc/security/selinux/policy.15
> /etc/security/selinux/src/policy.conf
> /usr/bin/checkpolicy:  loading policy configuration from
> /etc/security/selinux/src/policy.conf
> security:  4 users, 6 roles, 1194 types, 1 bools
> security:  30 classes, 263180 rules
> /usr/bin/checkpolicy:  policy configuration loaded
> /usr/bin/checkpolicy:  writing binary representation (version 15) to
> /etc/security/selinux/policy.15
> warning: discarding booleans and conditional rules
> /usr/sbin/load_policy /etc/security/selinux/policy.`cat 
> /selinux/policyvers`
> cat: /selinux/policyvers: No such file or directory
> /usr/sbin/load_policy:  security_load_policy failed
> make: *** [tmp/load] Error 3
> make: Leaving directory `/etc/security/selinux/src/policy'
> error: %post(policy-sources-1.9.2-12) scriptlet failed, exit status 2
>
> what do I do to solve this problem and I upgraded from FC2 T1 to FC2 T2
>
>
The list shows that /srlinux/polcyvers does not exist. This suggests 
that selinux was not enabled when you booted. That is,  that  you have  
selinux=0  on the  kernel line   (or as a boot parameter or 
/etc/sysconfig/selinux contains SELINUX=disabled.)
 Try this:
 boot with "enforcing=0" (without the  quotes and no selinux=0)
after booting and logging in as root,  get to a  terminal and
cd  /etc/security/selinux/src/policy
make load
make relabel   (this will take awhile, let it run)
reboot  (also with enforcing=0)

that should put you in "permissive mode"

Hope this helps,
Richard Hally