Description of problem: From RHEL4_Alpha2 Release Notes, selinux can be disabled at boot time through adding "selinux=0" option to kernel. But when I tried on LangleyPR, it caused "kernel panic". LangleyPR hardware info: x86/Xeon(dual 2.4G)/SCSI(aic7xxx) Version-Release number of selected component (if applicable): How reproducible: -- Install RHEL4_Alpha2_IA32 releases on LangleyPR -- Boot the installed system with setting "selinux=0" option to kernel -- ... EXT3-fs:recovery complete EXT3-fs: mounted filesystem with ordered data mode Freeing unused kernel memory: 1.80k freed Enforcing mode requested but no policy loaded, Halting now. Kernel panic: Attempted to kill init! -- System hangs up. Actual results: Setting "selinux=0" option to boot kernel will cause kernel panic. Expected results: Coordinating with Release Notes, selinux=0 option can work and disable selinux. Additional info:
You need to update the SysVinit package. There is a bug in the package that looks for the /etc/sysconfig/selinux file and if it exists but the kernel does not support selinux (selinux=0) the init script exist causing the kernel to crash. It should just return that SELinux is not running. So fixed in rawhide. SysVinit-2.85-23 Dan
Will the fix be integrated in the next RHEL4 release? thanks! Anli
Yes, You can remove the /etc/sysconfig/selinux file and the problem should go away also. Dan