From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@vger.kernel.org, Dan Walsh <dwalsh@redhat.com>
Subject: Re: [PATCH] python/semanage: Examples are no longer in the main semanage man page
Date: Tue, 5 Feb 2019 08:19:38 +0100 [thread overview]
Message-ID: <CAJfZ7=kWR-dMFu8djrOYRO_-Lc1rbk+29k5_v=P-R0eRwc==eg@mail.gmail.com> (raw)
In-Reply-To: <CAJfZ7=nUFYY9QLaArWAfLksvjB-xvvPwz2TvxuKPsTysSG5K=w@mail.gmail.com>
On Thu, Jan 31, 2019 at 11:06 PM Nicolas Iooss <nicolas.iooss@m4x.org> wrote:
>
> On Thu, Jan 31, 2019 at 8:41 PM Petr Lautrbach <plautrba@redhat.com> wrote:
> >
> > From: Dan Walsh <dwalsh@redhat.com>
> >
> > Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Indeed, commit 1925e1e91d99 ("Break the semanage man page into
> different man pages per category.") moved the examples in 2013.
>
> Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
Merged. Thanks
Nicolas
> > ---
> > 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
> >
prev parent reply other threads:[~2019-02-05 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 19:41 [PATCH] python/semanage: Examples are no longer in the main semanage man page Petr Lautrbach
2019-01-31 22:06 ` Nicolas Iooss
2019-02-05 7:19 ` Nicolas Iooss [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='CAJfZ7=kWR-dMFu8djrOYRO_-Lc1rbk+29k5_v=P-R0eRwc==eg@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=dwalsh@redhat.com \
--cc=plautrba@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).