On Wed, 2004-05-05 at 19:12 +1000, Dennis Gilmore wrote: > Once upon a time Wednesday 05 May 2004 6:32 pm, Rui Miguel Seabra wrote: > > I had to revert to 327 since 349 ignores selinux=0 > > > > I didn't try to add enforcing=0... > > > > Rui > I fixed this for me by changing /etc/sysconfig/selinux to selinux=disabled it > seems that in the mix there somewhere the kernel decided to ignore the > selinux=0 if /etc/sysconfig/selinux had enforcing in > > Dennis Setting SELINUX=disabled in /etc/sysconfig/selinux worked for me as well. I didn't have an /etc/sysconfig/selinux file at all prior to that. It seems that the selinux parameter on the command line was completely ignored. -- David T Hollis <dhollis@xxxxxxxxxxxxxx>
