From: Guido Trentalancia <guido@trentalancia.com>
To: selinux@tycho.nsa.gov
Subject: [PATCH] Further clarification of the usage of run_init in the manual page
Date: Tue, 19 Jul 2011 21:51:06 +0200 [thread overview]
Message-ID: <1311105066.2550.21.camel@vortex> (raw)
It's a very minor thing really, but I believe (on the basis of an
off-list question) that the manual page for policycoreutils/run_init can
be improved by the following short patch which aims to further clarify
the intended usage of such tool and mention that it caters for one
(somewhat hidden) compile-time option.
diff -pruN selinux-09062011/policycoreutils/run_init/run_init.8 selinux-09062011-run_init-auth-manpage/policycoreutils/run_init/run_init.8
--- selinux-09062011/policycoreutils/run_init/run_init.8 2011-05-09 01:04:17.075842476 +0200
+++ selinux-09062011-run_init-auth-manpage/policycoreutils/run_init/run_init.8 2011-06-09 23:06:53.350242852 +0200
@@ -9,6 +9,8 @@ run_init \- run an init script in the pr
.PP
Run a init script under the proper context, which is specified in
/etc/selinux/POLICYTYPE/contexts/initrc_context.
+It is generally used interactively as it requires either shadow or
+PAM user authentication (depending on compile-time options).
.SH FILES
/etc/passwd - user account information
.br
--
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.
next reply other threads:[~2011-07-19 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 19:51 Guido Trentalancia [this message]
2011-07-19 20:12 ` [PATCH] Further clarification of the usage of run_init in the manual page Eric Paris
2011-07-19 20:34 ` 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=1311105066.2550.21.camel@vortex \
--to=guido@trentalancia.com \
--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.