From: Steve Lawrence <slawrence@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: selinux man page fixes
Date: Tue, 01 Mar 2011 12:55:04 -0500 [thread overview]
Message-ID: <4D6D32F8.701@tresys.com> (raw)
In-Reply-To: <4D488B3F.8030203@redhat.com>
On 02/01/2011 05:37 PM, Daniel J Walsh wrote:
> diff --git a/libselinux/man/man8/selinux.8 b/libselinux/man/man8/selinux.8
> index 5caa592..1fc5b95 100644
> --- a/libselinux/man/man8/selinux.8
> +++ b/libselinux/man/man8/selinux.8
> @@ -1,7 +1,7 @@
> .TH "selinux" "8" "29 Apr 2005" "dwalsh@redhat.com" "SELinux Command Line documentation"
>
> .SH "NAME"
> -selinux \- NSA Security-Enhanced Linux (SELinux)
> +SELinux \- NSA Security-Enhanced Linux (SELinux)
>
> .SH "DESCRIPTION"
>
> @@ -62,12 +62,12 @@ compile-time tunable options and a set of runtime policy booleans.
> .B system-config-securitylevel
> allows customization of these booleans and tunables.
>
> -Many domains that are protected by SELinux also include selinux man pages explainging how to customize their policy.
> +Many domains that are protected by SELinux also include SELinux man pages explaining how to customize their policy.
>
> .SH FILE LABELING
>
> All files, directories, devices ... have a security context/label associated with them. These context are stored in the extended attributes of the file system.
> -Problems with SELinux often arise from the file system being mislabeled. This can be caused by booting the machine with a non selinux kernel. If you see an error message containing file_t, that is usually a good indicator that you have a serious problem with file system labeling.
> +Problems with SELinux often arise from the file system being mislabeled. This can be caused by booting the machine with a non SELinux kernel. If you see an error message containing file_t, that is usually a good indicator that you have a serious problem with file system labeling.
>
> The best way to relabel the file system is to create the flag file /.autorelabel and reboot. system-config-securitylevel, also has this capability. The restorcon/fixfiles commands are also available for relabeling files.
Acked-by: Steve Lawrence <slawrence@tresys.com>
Merged as of libselinux to 2.0.99
--
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.
prev parent reply other threads:[~2011-03-01 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 22:37 selinux man page fixes Daniel J Walsh
2011-03-01 17:55 ` Steve Lawrence [this message]
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=4D6D32F8.701@tresys.com \
--to=slawrence@tresys.com \
--cc=dwalsh@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.