From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2]: clarify the file_contexts.subs_dist configuration file usage
Date: Thu, 23 Aug 2012 09:28:28 -0400 [thread overview]
Message-ID: <50362FFC.1090103@tresys.com> (raw)
In-Reply-To: <201208201028.q7KASdj7014380@vivaldi39.register.it>
On 08/20/12 06:28, Guido Trentalancia wrote:
> Hello.
>
> The following "patch on patch", improves the current version of the file_contexts.subs_dist comments recently added by a v1 patch:
>
> Improve the comment at the top of the configuration file file_contexts.subs_dist.
>
> A name change might be considered too, if it proves to lead to further
> confusion.
>
> There might be pieces of documentation that could benefit from similar
> disambiguations.
>
> A manual page (userspace) is missing (one could easily be created by
> linking from file_contexts.5).
>
> Signed-off-by: Guido Trentalancia <guido@trentalancia.com>
> ---
> config/file_contexts.subs_dist | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> --- refpolicy-08092012-file_contexts.subs_dist-comment/config/file_contexts.subs_dist 2012-08-10 17:01:36.045451839 +0200
> +++ refpolicy-08092012-file_contexts.subs_dist-comment-v2/config/file_contexts.subs_dist 2012-08-20 13:18:35.568288286 +0200
> @@ -1,12 +1,22 @@
> -# This file can is used to configure base path aliases as in:
> +# This file can be optionally used to configure base path aliases
> +# for directories as in:
> #
> -# /aliased_path /original_path_as_configured_in_file_contexts
> +# /aliased_path /original_path_as_configured_in_file_contexts
> #
> # where original_path_as_configured_in_file_contexts is a base
> -# path being used in the main file_contexts configuration file.
> +# path being used in the file_contexts SELinux policy configuration
> +# file.
> #
> -# It does not perform substitutions as done by sed(1), for
> -# example, but aliasing.
> +# It does not perform substitutions as done by sed(1), for example,
> +# but aliasing (or in other words it creates equivalences between
> +# different base directories).
> +#
> +# With reference to the example syntax shown above, /aliased_path and
> +# all files and directories located under it will be labelled exactly
> +# as /original_path_as_configured_in_file_contexts and all files and
> +# directories located under it.
> +#
> +# See file_contexts(5) for further information.
> #
> /lib32 /lib
> /lib64 /lib
This isn't applying for me.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-08-23 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 10:28 [refpolicy] [PATCH v2]: clarify the file_contexts.subs_dist configuration file usage Guido Trentalancia
2012-08-23 13:28 ` Christopher J. PeBenito [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=50362FFC.1090103@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.