From: Mike Edenfield <kutulu@kutulu.org>
To: Jim Meyering <jim@meyering.net>
Cc: "Vikram Noel Ambrose" <noel.ambrose@gmail.com>,
bug-coreutils@gnu.org, selinux@tycho.nsa.gov,
472590@bugs.debian.org, "Ondřej Vašík" <ovasik@redhat.com>
Subject: Re: RFC: changing the "+" in ls -l output to be "." or "+"
Date: Fri, 24 Oct 2008 09:19:07 -0400 [thread overview]
Message-ID: <4901CB4B.3030306@kutulu.org> (raw)
In-Reply-To: <87mygumq37.fsf@rho.meyering.net>
Jim Meyering wrote:
> A desire for compatibility makes "+" look good.
> "." is appealing for SELinux-only because it's inconspicuous.
Speaking as a fairly new SELinux user/admin, having a "."
next to every file in my ls output is just as useful or
non-useful as having a "+" next to them, so does it really
buy anything? I end up needing -Z either way.
Based on the kind of real-world problems I've had, the most
useful thing ls could tell me about a file on my SELinux
system would be that it *should* have a label and *doesn't*,
something like:
if ( selinux_enabled )
if ( label == NULL || label == fs.defaultlabel )
use "!"
else
use " "
else if ( anything else )
use "+"
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-10-24 13:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 4:23 ls in Debian/Unstable Russell Coker
2008-03-25 14:09 ` Casey Schaufler
2008-03-25 15:08 ` Jim Meyering
2008-03-25 21:22 ` Russell Coker
[not found] ` <20080325173116.GQ2626@mathom.us>
2008-03-25 21:24 ` Bug#472590: " Russell Coker
2008-03-25 21:28 ` Jim Meyering
[not found] ` <20080325234310.GR2626@mathom.us>
2008-03-26 5:12 ` Russell Coker
2008-03-31 9:02 ` Jim Meyering
2008-03-31 9:23 ` Russell Coker
2008-03-31 9:43 ` Jim Meyering
2008-04-02 20:33 ` RFC: changing the "+" in ls -l output to be "." or "+" Jim Meyering
2008-10-23 12:20 ` Jim Meyering
2008-10-24 3:18 ` Vikram Noel Ambrose
2008-10-24 7:04 ` Jim Meyering
2008-10-24 13:19 ` Mike Edenfield [this message]
2008-10-26 7:46 ` Russell Coker
2008-10-26 8:09 ` Jim Meyering
2008-10-31 13:37 ` Daniel J Walsh
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=4901CB4B.3030306@kutulu.org \
--to=kutulu@kutulu.org \
--cc=472590@bugs.debian.org \
--cc=bug-coreutils@gnu.org \
--cc=jim@meyering.net \
--cc=noel.ambrose@gmail.com \
--cc=ovasik@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.