On Thu, Jan 31, 2019 at 11:06 PM Nicolas Iooss <nicolas.iooss@xxxxxxx> wrote:
>
> On Thu, Jan 31, 2019 at 8:41 PM Petr Lautrbach <plautrba@xxxxxxxxxx> wrote:
> >
> > From: Dan Walsh <dwalsh@xxxxxxxxxx>
> >
> > Signed-off-by: Petr Lautrbach <plautrba@xxxxxxxxxx>
>
> 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@xxxxxxx>
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
> >
