From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Russell Coker <russell@coker.com.au>,
Daniel J Walsh <dwalsh@redhat.com>
Subject: [SEMANAGE] Manpage reorganization
Date: Thu, 16 Mar 2006 09:23:20 -0500 [thread overview]
Message-ID: <441974D8.7030706@cornell.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Hi, this patch does the following:
Existing manpages:
===============
- remove listing of objects in each dbase function - this doesn't scale,
I have to change it in 10+ places to add a new object, and it's really
annoying. Just present the function template, and then we'll have
per-object overview pages that link to that template, so the user won't
be confused [ see new pages added below ].
- move the controlling page from *_user_local.3 to an object-neutral page:
semanage_add.3, semanage_modify.3, semanage_list.3 ... etc
- fix some allignment issues
- add "(3)" to references to other manpages so man2html makes links
New manpages:
============
- add an overview page for each object type, which gives all the
functions for that object: semanage_fcontext.3 semanage_user.3,
semanage_seuser.3, semanage_bool.3..etc. This page becomes more valuable
when the functions listed there are also hyperlinks.
========
We should run man2html over all those pages, and host the result
somewhere, once it's more complete.
Russell suggested James Morris' page (selinuxnews.org?)
I also plan to write a semanage.3 page.
[-- Attachment #2: libsemanage.doc.diff.bz2 --]
[-- Type: application/x-bzip, Size: 7461 bytes --]
next reply other threads:[~2006-03-16 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 14:23 Ivan Gyurdiev [this message]
2006-03-16 15:48 ` [SEMANAGE] Manpage reorganization James Morris
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=441974D8.7030706@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=dwalsh@redhat.com \
--cc=russell@coker.com.au \
--cc=sds@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.