All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage
Date: Wed, 15 Aug 2012 10:02:26 +0200	[thread overview]
Message-ID: <20120815080226.GA32379@siphos.be> (raw)
In-Reply-To: <502A3EAE.2060905@tresys.com>

On Tue, Aug 14, 2012 at 08:03:58AM -0400, Christopher J. PeBenito wrote:
> On 08/10/12 09:13, Guido Trentalancia wrote:
> > Add a comment at the top of the configuration file file_contexts.subs_dist
> > to clarify that it performs aliasing and not substitutions in the
> > strict sense of the word.
> > 
> > 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
> > considerations.
> > 
> > Also note that a specific manual page is missing.
> > 
> > Signed-off-by: Guido Trentalancia <guido@trentalancia.com>
> > ---
> >  config/file_contexts.subs_dist |   10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff -pruN refpolicy-08092012/config/file_contexts.subs_dist refpolicy-08092012-file_contexts.subs_dist-comment/config/file_contexts.subs_dist
> > --- refpolicy-08092012/config/file_contexts.subs_dist    2012-06-21 20:10:29.011803405 +0200
> > +++ refpolicy-08092012-file_contexts.subs_dist-comment/config/file_contexts.subs_dist 2012-08-10 17:01:36.045451839 +0200
> > @@ -1,3 +1,13 @@
> > +# This file can is used to configure base path aliases as in:
> > +#
> > +# /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.
> > +#
> > +# It does not perform substitutions as done by sed(1), for
> > +# example, but aliasing.
> > +#
> >  /lib32 /lib
> >  /lib64 /lib
> >  /run /var/run
> 
> Merged.

This seems to break policycoreutils:

# semanage fcontext -l
/usr/sbin/semanage: too many values to unpack (expected 2)

Undoing the comment change fixes things again.

Wkr,
	Sven Vermeulen

  reply	other threads:[~2012-08-15  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 13:13 [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage Guido Trentalancia
2012-08-14 12:03 ` Christopher J. PeBenito
2012-08-15  8:02   ` Sven Vermeulen [this message]
2012-08-15  8:13     ` Guido Trentalancia
2012-08-15  8:20       ` Sven Vermeulen
2012-08-15  8:38         ` Guido Trentalancia
2012-08-15  8:45           ` Sven Vermeulen
2012-08-15  9:48             ` Guido Trentalancia
  -- strict thread matches above, loose matches on Subject: below --
2012-08-18 12:30 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=20120815080226.GA32379@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --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.