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 01/15] Support /usr/sbin/alsactl location too (fex. Gentoo, Slackware, Arch)
Date: Thu, 10 Mar 2011 14:33:46 +0100	[thread overview]
Message-ID: <20110310133346.GA12988@siphos.be> (raw)
In-Reply-To: <1299707886.2974.6.camel@tesla.lan>

On Wed, Mar 09, 2011 at 10:58:06PM +0100, Guido Trentalancia wrote:
> Local symlink ? Or at least ifdef in the file context file ? I mean if
> refpolicy has to cater for every single case of different location for
> every different distribution or installation...

I agree, but I think that /usr/sbin/alsactl is the correct location (as alsa
is not a prerequisite in order to succesfully boot a system, so no
requirement to be in /sbin). It is also used by various distributions, not
just one.

If the reference policy wants to be consistent in its file context
definitinos, it should base this on something, not on the first one who
suggested a location.

I try to only suggest file context definitions that are matched by 
- a purely single distribution (with an ifdef)
- several (at least 3) distributions (which are not related to each other)
- upstream (for instance locations documented by the package itself)

If it is not the intention to have a functional file context, but rather
inform policy developers on how it could be (i.e. know that the alsactl
binary should be alsa_exec_t) that's fine with me too - just say it ;-)

Wkr,
	Sven Vermeulen

  reply	other threads:[~2011-03-10 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:05 [refpolicy] [PATCH 01/15] Support /usr/sbin/alsactl location too (fex. Gentoo, Slackware, Arch) Sven Vermeulen
2011-03-09 21:58 ` Guido Trentalancia
2011-03-10 13:33   ` Sven Vermeulen [this message]
2011-03-10 15:06     ` Guido Trentalancia
2011-03-22 12:38 ` Christopher J. PeBenito

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=20110310133346.GA12988@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.