Blame SOURCES/0002-semanage-man-page-1084390.patch

a13ffa
From d9d9d7825ccf519b79878277669d4d311a686bb6 Mon Sep 17 00:00:00 2001
a13ffa
From: Miroslav Grepl <mgrepl@redhat.com>
a13ffa
Date: Mon, 29 Sep 2014 09:45:21 +0200
a13ffa
Subject: [PATCH 1/5] Fix semanage man page to talk about  semanage-* (8) man
a13ffa
 pages.
a13ffa
a13ffa
---
a13ffa
 policycoreutils/semanage/semanage.8 | 6 +++---
a13ffa
 1 file changed, 3 insertions(+), 3 deletions(-)
a13ffa
a13ffa
diff --git a/policycoreutils/semanage/semanage.8 b/policycoreutils/semanage/semanage.8
a13ffa
index fd27cf2..5d09d92 100644
a13ffa
--- a/policycoreutils/semanage/semanage.8
a13ffa
+++ b/policycoreutils/semanage/semanage.8
a13ffa
@@ -51,9 +51,9 @@ to SELinux user identities (which controls the initial security context
a13ffa
 assigned to Linux users when they login and bounds their authorized role set)
a13ffa
 as well as security context mappings for various kinds of objects, such
a13ffa
 as network ports, interfaces, and nodes (hosts) as well as the file
a13ffa
-context mapping. See the EXAMPLES section below for some examples
a13ffa
-of common usage.  Note that the semanage login command deals with the
a13ffa
-mapping from Linux usernames (logins) to SELinux user identities,
a13ffa
+context mapping. See the EXAMPLES section of semanage-* (8) man pages 
a13ffa
+for some examples of common usage.  Note that the semanage login command 
a13ffa
+deals with the mapping from Linux usernames (logins) to SELinux user identities,
a13ffa
 while the semanage user command deals with the mapping from SELinux
a13ffa
 user identities to authorized role sets.  In most cases, only the
a13ffa
 former mapping needs to be adjusted by the administrator; the latter
a13ffa
-- 
a13ffa
2.1.0
a13ffa