SELinux-Refpolicy Archive on lore.kernel.org
 help / color / Atom feed
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
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

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11  3:02 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

SELinux-Refpolicy Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
		selinux-refpolicy@vger.kernel.org
	public-inbox-index selinux-refpolicy

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git