If SELINUX caused problems after a brand new installation, than it conflicts with one or more packages - SELINUX is for example known to play difficult with the Apache server sometimes. So if you reinstall with the same combination of packages and disable SELINUX in the same way as you did before then you can easily come to the same result.
If you can run Linux in rescue mode by booting from the installer DVD, then login to a root shell (rescue mode offers that option) and remount the hard drive with the new installation in writeable mode:
# this should give a list of your HDD devices
$ fdisk -l
# knowing the name of your device you should remount to writeable
# (it should have been mounted in read-only mode)
$ mount -remount <your-device> <mount point>
This way you can overwrite SELINUX settings by hand:
# goto the SELINUX config directory and open the config file
$ cd <mount point>/etc/selinux
$ vi config
Modify it to look like this (only uncommented lines count):
---------------------------------------------------------
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
# SETLOCALDEFS= Check local definition changes
SETLOCALDEFS=0
---------------------------------------------------------
After rebooting SELINUX will be entirely disabled. If the problem still exists after that, than SELINUX is just a part of the problem.
Hope this helps,
Regards,
SIMP
Linux Archive
