On Wed, 2 Oct 2013, Chase, John wrote:
What else must be done to get the RHEL vm to come up with
SELinux showing "disabled" instead of "permissive" in
response to a 'getenforce' command?
adding a line to the relevant grub stanza comes to mind.
Something like this
title SE-Linux Test System
root (hd0,0)
kernel /boot/vmlinuz-2.4.20-selinux-2003040709 ro
root=/dev/hda1 nousb enforcing=0
#initrd /boot/initrd-2.4.20-selinux-2003040709.img
AND in /etc/selinux/config
SELINUX=disabled
but <include standard disclaimer>
a support person telling you to disable SELinux protections
for anything but diagnostic purposes needs to be escalated
past if they try to suggest that for a production unit
-- Russ herrold
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
