From: Dominick Grift <domg472@gmail.com>
To: Murray McAllister <mmcallis@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>,
Daniel Walsh <dwalsh@redhat.com>, Eric Paris <eparis@redhat.com>,
James Morris <jmorris@namei.org>
Subject: Re: user guide: troubleshooting chapter
Date: Wed, 29 Oct 2008 10:22:17 +0100 [thread overview]
Message-ID: <1225272137.26092.2.camel@rawhide.grift.internal> (raw)
In-Reply-To: <4907D37F.3090404@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
On Wed, 2008-10-29 at 13:07 +1000, Murray McAllister wrote:
> Thanks for any ideas.
Issues often happen due to bad labels. You may want to touch on
autorelabel, fixfiles, restorecon and invalid types like unlabeled_t,
file_t etc. The first thing i always check is to see if the source and
target context look valid.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-29 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 3:07 user guide: troubleshooting chapter Murray McAllister
2008-10-29 9:22 ` Dominick Grift [this message]
2008-10-31 13:40 ` Daniel J Walsh
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=1225272137.26092.2.camel@rawhide.grift.internal \
--to=domg472@gmail.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=mmcallis@redhat.com \
--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.