All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Trentalancia <guido@trentalancia.com>
To: Eric Paris <eparis@parisplace.org>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	russell@coker.com.au, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: policycoreutils manpages needed
Date: Mon, 12 Sep 2011 23:28:04 +0200	[thread overview]
Message-ID: <1315862884.2223.33.camel@vortex> (raw)
In-Reply-To: <CACLa4ptfSU3obZ8OyMVFfKDsqwLQn58-O9YRUbCyU8=mLzn=tA@mail.gmail.com>

Hi Eric !

On Thu, 2011-09-01 at 21:52 -0400, Eric Paris wrote:
> On Thu, Sep 1, 2011 at 5:21 PM, Guido Trentalancia
> <guido@trentalancia.com> wrote:
> > On Thu, 2011-09-01 at 09:42 -0400, Daniel J Walsh wrote:
> >> On 09/01/2011 01:09 AM, Russell Coker wrote:
> >> > Has anyone written manpages for genhomedircon, sepolgen-ifgen, and
> >> > seunshare? If not is there someone with some spare time and man
> >> > page writing skill?
> >> >
> >> We have man pages for genhomedircon and seunshare.  Although the
> >> genhomedircon man page is rather sparse.
> >
> > If help is needed for manual pages, I can have a look and spare some
> > time. I can start with genhomedircon as suggested by Dan unless other
> > ideas are brought forward...
> 
> Just make sure you look at the 'queue' branch of the upstream repo
> rather than the 'master' branch.  I'm pretty sure some of the man
> pages Dan mentioned only exist in the queue branch.

Apparently, there isn't a massive difference for the manual pages
between the master and the queue branches.

In particular there are no new manual pages being introduced in the
queue branch (although there are some modifications to existing pages
mainly due to modifications in the tools).

I would like to take this opportunity to suggest that we create manual
pages for configuration files where possible (none available at the
moment ?!?).

For example, the very first one I would like to have is
semanage.conf.5. 

Then we could also create restorecond.conf.5 and restorecond_user.conf.5
(both of them should be trivial).

There might be very slight improvements possible for the seunshare
manual page. The manual pages for sepolgen* are missing and therefore
will need to be created from scratch. The manual page for sandbox.8
could be improved by mentioning that a configuration file exists in
$(DESTDIR)/etc/sysconfig/sandbox (along with a manual page
sandbox.conf.5).

That said, I am now going to start creating semanage.conf.5...

Regards,

Guido


--
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.

  reply	other threads:[~2011-09-12 21:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01  5:09 policycoreutils manpages needed Russell Coker
2011-09-01 13:42 ` Daniel J Walsh
2011-09-01 21:21   ` Guido Trentalancia
2011-09-02  1:52     ` Eric Paris
2011-09-12 21:28       ` Guido Trentalancia [this message]
2011-09-12 22:03         ` Eric Paris
2011-09-13  5:00         ` [RFC] semanage.conf manual page (was Re: policycoreutils manpages needed) Guido Trentalancia
2011-09-13  5:27           ` Guido Trentalancia
2011-09-13 16:03             ` [RFC v2] semanage.conf manual page (was Re: [RFC] semanage.conf manual page) Guido Trentalancia
2011-09-15  4:51               ` [PATCH v3] semanage.conf manual page Guido Trentalancia
2011-09-19 11:30                 ` Daniel J Walsh
2011-09-16  7:26         ` policycoreutils manpages needed Guido Trentalancia
2011-09-16 16:15           ` Richard Haines
2011-09-12  4:48   ` [PATCH] genhomedircon installation and manual page improvements (was Re: policycoreutils manpages needed) Guido Trentalancia

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=1315862884.2223.33.camel@vortex \
    --to=guido@trentalancia.com \
    --cc=dwalsh@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=russell@coker.com.au \
    --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.