From: Paul Moore <paul.moore@hp.com>
To: Mike Edenfield <kutulu@kutulu.org>
Cc: SELinux Mailing List <selinux@tycho.nsa.gov>
Subject: Re: Help: SELinux causing(?) boot failures...
Date: Fri, 8 Aug 2008 12:51:45 -0400 [thread overview]
Message-ID: <200808081251.45453.paul.moore@hp.com> (raw)
In-Reply-To: <489C6A4F.3020704@kutulu.org>
On Friday 08 August 2008 11:46:23 am Mike Edenfield wrote:
> The reason I strongly suspect SELinux is the problem (or at least a
> major factor), is that adding "selinux=0" to my boot command line
> corrects the problem, and the system boots fine. Everything appears
> to be installed and configured correctly, except obviously SELinux is
> now disabled. The filesystems are all labeled correctly, and even on
> the failing boot the AVC messages display the correct labels, like
> tty_device_t and urandom_device_t.
Hi Mike,
In general, you are better off using "enforcing=0", which keeps SELinux
enabled but puts it into permissive mode, on the kernel command line
instead of "selinux=0", which disables SELinux entirely. Have you
tried rebooting with "enforcing=0" and capturing the AVC messages from
the console/audit/syslog output and seeing if anything looks awry? If
not go ahead and do so and send them to the list, this will tell us
what actions are being denied and why.
--
paul moore
linux @ hp
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-08-08 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 15:46 Help: SELinux causing(?) boot failures Mike Edenfield
2008-08-08 16:51 ` Paul Moore [this message]
2008-08-08 17:19 ` Mike Edenfield
2008-08-08 18:01 ` Paul Moore
2008-08-08 18:13 ` Justin Mattock
2008-08-08 23:03 ` Russell Coker
2008-08-14 16:58 ` Stephen Smalley
2008-08-14 19:21 ` Mike Edenfield
2008-08-14 20:24 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808081251.45453.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=kutulu@kutulu.org \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.