From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Add openrc support to init_startstop_service
Date: Wed, 27 May 2015 13:04:37 -0400 [thread overview]
Message-ID: <5565F925.9070402@tresys.com> (raw)
In-Reply-To: <20150527165132.GA14860@x131e>
On 5/27/2015 12:51 PM, Dominick Grift wrote:
> On Wed, May 27, 2015 at 12:48:18PM -0400, Christopher J. PeBenito wrote:
>> On 5/25/2015 6:02 AM, Jason Zaman wrote:
>>> Adds the openrc rules in ifdef distro_gentoo to transition
>>> to run_init correctly.
>>
>> I'm fine with this set except one note below.
>>
>
> <snip>
>
>>
>> "spec" means setexeccon(), instead of type_transition, so this should
>> drop the "spec" from the name. Same thing in the caller below.
>>
>
> Just a quick comment from an innocent bystander:
>
> I appreciate that it is what it is, but i don't find it intuitive and in my personal policy i use "automatic versus manual" transition
It's so infrequently used that I haven't thought about it much. I'm
open to considering naming changes as long as it doesn't require
changing a ton of interfaces. i.e. "domtrans" by itself would have to
continue to mean domain transition via type_transition. There's not
even an official naming convention for dyntransition interfaces since
none exist (that is, none that only do dyntransition).
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2015-05-27 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 10:02 [refpolicy] [PATCH] Add openrc support to init_startstop_service Jason Zaman
2015-05-27 16:48 ` Christopher J. PeBenito
2015-05-27 16:51 ` Dominick Grift
2015-05-27 17:04 ` Christopher J. PeBenito [this message]
2015-05-27 17:07 ` Dominick Grift
2015-05-27 17:22 ` Jason Zaman
2015-05-27 17:33 ` Christopher J. PeBenito
2015-05-27 17:51 ` Jason Zaman
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=5565F925.9070402@tresys.com \
--to=cpebenito@tresys.com \
--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.