From: dominick.grift@gmail.com (Dominick Grift)
Date: Tue, 14 Jan 2014 23:23:47 +0100
Subject: [refpolicy] RFC: direct_init_entry breaks direct_initrc
In-Reply-To: <52D5A197.8010805@tresys.com>
References: <1386691021.18689.75.camel@d30> <52D54215.3040707@tresys.com>
	<1389708128.28251.54.camel@x220.localdomain>
	<52D54546.8010308@tresys.com>
	<1389724229.28251.74.camel@x220.localdomain>
	<52D5A197.8010805@tresys.com>
Message-ID: <1389738227.4012.2.camel@x220.localdomain>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On Tue, 2014-01-14 at 15:44 -0500, Christopher J. PeBenito wrote:
> 
> I think you may be able to drop the direct_run_init attribute and put the domtrans you added in the init_run_daemon() interface instead.
> 

Right, i also got rid of direct_init because was a lose end as well

It builds but still not actually tested

Enclosed i another try:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fix-directinitrc-and-make-it-also-apply-to-unconfine.patch
Type: text/x-patch
Size: 4791 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20140114/0dc288b5/attachment.bin