From: sven.vermeulen@siphos.be (Sven Vermeulen)
Date: Sun, 26 Feb 2012 13:24:52 +0100
Subject: [refpolicy] Build of 20120215 fails with unknown role system_r
In-Reply-To: <4F49FAD9.80102@windriver.com>
References: <20120225100547.GA28560@siphos.be> <4F49FAD9.80102@windriver.com>
Message-ID: <20120226122452.GB22698@siphos.be>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On Sun, Feb 26, 2012 at 05:26:49PM +0800, Harry Ciao wrote:
[...]
> system_r is actually defined in kernel.te. By default, there are only a 
> limited number of modules that would be built into base.pp and its 
> declaration happens before its first reference :
> 
> $ grep "= base" policy/modules.conf
> corecommands = base
> corenetwork = base
> devices = base
> domain = base
> files = base
> filesystem = base
> kernel = base
> mcs = base
> mls = base
> selinux = base
> terminal = base
> ubac = base

Well, I'm currently looking at using the default set for our base policy
(which seems to work well) but is the base set something we need to fix (as
in, users of refpolicy shouldn't update the list of modules belonging to
base) or is it something configurable?

Wkr,
	Sven Vermeulen