Tom London wrote:
On 4/27/06, Tom London <selinux(a)gmail.com> wrote:
> I can verify this. I separately updated to today's 'selinux-policy*'
> packages, and check /etc/selinux/config before and afterwards.
Could the offending script be the postuninstall script of selinux-policy:
The problem was in the preceding policy package that did not have the if
[ $1 = 0]; then
Call so when it got updated this code executed. IE the spec file
thought it was being updated. The newer policy packages should handle
postuninstall scriptlet (using /bin/sh):
if [ $1 = 0 ]; then
setenforce 0 2> /dev/null
if [ ! -s /etc/selinux/config ]; then
echo "SELINUX=disabled" > /etc/selinux/config
sed -i 's/^SELINUX=.*/SELINUX=disabled/g'
I also noticed that after the 'yum update', my system was in
fedora-selinux-list mailing list