From: Chris PeBenito <chpebeni@linux.microsoft.com>
To: russell@coker.com.au, selinux-refpolicy@vger.kernel.org
Subject: Re: [refpolicy3 RFC] Drop suffixes?
Date: Mon, 27 Mar 2023 08:32:53 -0400 [thread overview]
Message-ID: <14aa07c3-5517-9855-5273-71ad1bef17df@linux.microsoft.com> (raw)
In-Reply-To: <4896093.0VBMTVartN@xev>
On 3/25/2023 05:15, Russell Coker wrote:
> On Saturday, 25 March 2023 05:10:10 AEDT Chris PeBenito wrote:
>> I am considering dropping the suffixes from users, roles, and types.
>> init_t would become init, user_r would become user, etc.
>
> Even when the syntax prevents the compiler from being confused there is a
> benefit to avoiding user confusion. So having user_r:user_t change to
> user:user would be bad IMHO.
>
> 22 years ago this might have been justified by reducing RAM use or something
> but that doesn't apply now. What's the motivation for this?
Since refpolicy3 is a major change, I've been reexamining past
decisions. Now is the time to make significant changes.
--
Chris PeBenito
prev parent reply other threads:[~2023-03-27 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 18:10 [refpolicy3 RFC] Drop suffixes? Chris PeBenito
2023-03-24 18:31 ` Dominick Grift
2023-03-25 9:15 ` Russell Coker
2023-03-27 12:32 ` 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=14aa07c3-5517-9855-5273-71ad1bef17df@linux.microsoft.com \
--to=chpebeni@linux.microsoft.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).