From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/3] Add in substitutions for /usr/local
Date: Tue, 31 Jul 2012 14:51:44 -0400 [thread overview]
Message-ID: <50182940.3090800@tresys.com> (raw)
In-Reply-To: <1343495174-6852-2-git-send-email-sven.vermeulen@siphos.be>
On 07/28/12 13:06, Sven Vermeulen wrote:
> Translate any paths towards /usr/local as if they were to /usr.
>
> Since the substitutions aren't chained together, we need to define the rules for
> the individual /usr/local/lib* directories as well.
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> config/file_contexts.subs_dist | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/config/file_contexts.subs_dist b/config/file_contexts.subs_dist
> index 32b87a4..72a7a0f 100644
> --- a/config/file_contexts.subs_dist
> +++ b/config/file_contexts.subs_dist
> @@ -4,4 +4,7 @@
> /run/lock /var/lock
> /usr/lib32 /usr/lib
> /usr/lib64 /usr/lib
> +/usr/local /usr
I'm reluctant to make this substitution. From my experience, too many things don't seem follow this well.
> +/usr/local/lib32 /usr/lib
> +/usr/local/lib64 /usr/lib
I'd be more accepting of this change.
> /var/run/lock /var/lock
>
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-07-31 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 17:06 [refpolicy] [PATCH 0/3] Introduce substitution for /usr/local Sven Vermeulen
2012-07-28 17:06 ` [refpolicy] [PATCH 1/3] Add in substitutions " Sven Vermeulen
2012-07-31 18:51 ` Christopher J. PeBenito [this message]
2012-07-31 19:14 ` Sven Vermeulen
2012-07-28 17:06 ` [refpolicy] [PATCH 2/3] Update file contexts to match substitution Sven Vermeulen
2012-07-28 17:06 ` [refpolicy] [PATCH 3/3] Update file contexts to match /usr/local transition Sven Vermeulen
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=50182940.3090800@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.