From: Chris PeBenito <pebenito@ieee.org>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: systemd_generator_t vs systemd_generator_type
Date: Tue, 14 Apr 2020 11:06:07 -0400 [thread overview]
Message-ID: <ee3f03ff-d42b-9507-668b-36e22aadeb3d@ieee.org> (raw)
In-Reply-To: <1717302.MpC4nazLU5@liv>
On 4/10/20 11:02 PM, Russell Coker wrote:
> This combination of names is confusing. As a general rule I think we
> shouldn't have a type name be a substring of an attribute name. Having an
> attribute name as a substring of a type name is less of an issue but still
> best avoided.
>
> /lib/systemd/system-generators/systemd-bless-boot-generator
> /lib/systemd/system-generators/systemd-cryptsetup-generator
> /lib/systemd/system-generators/systemd-debug-generator
> /lib/systemd/system-generators/systemd-getty-generator
> /lib/systemd/system-generators/systemd-hibernate-resume-generator
> /lib/systemd/system-generators/systemd-rc-local-generator
> /lib/systemd/system-generators/systemd-run-generator
> /lib/systemd/system-generators/systemd-system-update-generator
> /lib/systemd/system-generators/systemd-veritysetup-generator
> /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-
> generator
>
> Above are the generators on my system that run as systemd_generator_t. Would
> systemd_generator_generic_t/systemd_generator_generic_exec_t be an OK name?
I'd accept a patch for this.
--
Chris PeBenito
prev parent reply other threads:[~2020-04-14 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 3:02 systemd_generator_t vs systemd_generator_type Russell Coker
2020-04-14 15:06 ` Chris PeBenito [this message]
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=ee3f03ff-d42b-9507-668b-36e22aadeb3d@ieee.org \
--to=pebenito@ieee.org \
--cc=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).