I ran the following 4 commands to disable the firewall. Everything is good while the Virtualbox VM is running, but after rebooting the VM I noticed that the config file that was modified with the 4th command below reverted back to it's original state, where the SELINUX variable was set to enforcing. I'm very sure that I saved the file with <Escape> then wq!, I verified by running cat against the config file after the modification. After the VM was rebooted I also noticed that the "chkconfig --list iptables" command returned values of on, signifying that the firewall wasn't completely disabled. I'm no expert in Linux, is there more that needs to be done, other than the commands below to disabled the firewall across reboots of the OS?, what am I missing?
[root@collabn1 ~]# service iptables stop
iptables: Flushing firewall rules: [ OK ]
iptables: Setting chains to policy ACCEPT: filter [ OK ]
iptables: Unloading modules: [ OK ]
[root@collabn1 ~]# chkconfig iptables off
[root@collabn1 ~]# chkconfig --list iptables
iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@collabn1 ~]# vi /etc/selinux/config
# 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 - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Targeted processes are protected,
# mls - Multi Level Security protection.
SELINUXTYPE=targeted