From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Cc: Dan Walsh <dwalsh@redhat.com>, Petr Lautrbach <plautrba@redhat.com>
Subject: [PATCH] python/semanage: Examples are no longer in the main semanage man page
Date: Thu, 31 Jan 2019 20:41:40 +0100 [thread overview]
Message-ID: <20190131194140.3785-1-plautrba@redhat.com> (raw)
From: Dan Walsh <dwalsh@redhat.com>
Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
---
python/semanage/semanage.8 | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/python/semanage/semanage.8 b/python/semanage/semanage.8
index 0bdb90f4..0cdcfccd 100644
--- a/python/semanage/semanage.8
+++ b/python/semanage/semanage.8
@@ -57,9 +57,8 @@ to SELinux user identities (which controls the initial security context
assigned to Linux users when they login and bounds their authorized role set)
as well as security context mappings for various kinds of objects, such
as network ports, interfaces, infiniband pkeys and endports, and nodes (hosts)
-as well as the file context mapping. See the EXAMPLES section below for some
-examples of common usage. Note that the semanage login command deals with the
-mapping from Linux usernames (logins) to SELinux user identities,
+as well as the file context mapping. Note that the semanage login command deals
+with the mapping from Linux usernames (logins) to SELinux user identities,
while the semanage user command deals with the mapping from SELinux
user identities to authorized role sets. In most cases, only the
former mapping needs to be adjusted by the administrator; the latter
--
2.20.1
next reply other threads:[~2019-01-31 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 19:41 Petr Lautrbach [this message]
2019-01-31 22:06 ` [PATCH] python/semanage: Examples are no longer in the main semanage man page Nicolas Iooss
2019-02-05 7:19 ` Nicolas Iooss
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=20190131194140.3785-1-plautrba@redhat.com \
--to=plautrba@redhat.com \
--cc=dwalsh@redhat.com \
--cc=selinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).