On Thu, 1 Apr 2004 02:46, Gene Czarcinski <gene@xxxxxxxxx> wrote: > > I had similar problems. Clean install of test2 with selinux in enforcing > > mode followed by a yum update. Many of the postinstall scripts reported > > failures and after a reboot (to boot the new kernel that didn't get > > installed) lots of things were very broken. Permissions on directories > > in /var were all messed up (as root I couldn't cd to /var/log to try to > > figure out what was going). So I did a clean install of test2 again, > > setting selinux to warn only, and things are much happier. It seems like > > the default policy of selinux kept many files from being updated > > properly. > > > > Let me know if you file a bug report so I can add to it. > > This is an selinux - rpm problem ... see: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119538 That one is due to installing packages as staff_r. The general idea with SE Linux is that you use sysadm_r for such things. In Fedora su and sudo should change to sysadm_r. If you login at the console as root you will get sysadm_r. It should just work. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page
