Once upon a time, Bill Nottingham nott...@redhat.com said:
We have an existing bug where if you're in single-user mode, and
SELinux is active, various commands don't print to the console.
The root of this is the single-user shell isn't running in the
right SELinux context, as there's nothing
Chris Adams (cmad...@hiwaay.net) said:
How about moving /usr/bin/runcon to /bin and using that to call bash
instead?
The problem is that the context it needs to run at isn't static; it
depends on the policy of the machine. Hence, you don't want to hardcode
a runcon call in the script.
Bill
--
On 10-01-22 13:29:11, Bruno Wolff III wrote:
On Fri, Jan 22, 2010 at 13:15:04 -0500,
Tony Nelson tonynel...@georgeanelson.com wrote:
Put SELinux into Permissive mode for single-user mode? Or just
print a suggestion to do that? (I'd think that SELinux would
normally be perceived as
