From mboxrd@z Thu Jan  1 00:00:00 1970
From: sven.vermeulen@siphos.be (Sven Vermeulen)
Date: Thu, 10 Mar 2011 14:33:46 +0100
Subject: [refpolicy] [PATCH 01/15] Support /usr/sbin/alsactl location
 too (fex. Gentoo, Slackware, Arch)
In-Reply-To: <1299707886.2974.6.camel@tesla.lan>
References: <20110309210524.GA4658@siphos.be>
	<1299707886.2974.6.camel@tesla.lan>
Message-ID: <20110310133346.GA12988@siphos.be>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

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