From: Robert Bihlmeyer <robbe@orcus.priv.at>
To: selinux@tycho.nsa.gov
Subject: Re: busybox ls
Date: 27 Apr 2003 18:25:35 +0200 [thread overview]
Message-ID: <87k7df9abk.fsf@orcus.priv.at> (raw)
In-Reply-To: <200304270213.57411.russell@coker.com.au>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Russell Coker <russell@coker.com.au> writes:
> Any suggestions on which option switches I should use for equivalent
> of --sid and --context functionality?
Maybe -K for --context (upcase as not to "kollide" with GNU ls's -k
option)? -O is also viable, but I prefer -K as lame as it is.
I think if whatever you use for --context is used together with -n
("numeric ids") the effect of --sid should occur.
--
Robbe
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-04-27 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 16:13 busybox ls Russell Coker
2003-04-27 16:25 ` Robert Bihlmeyer [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=87k7df9abk.fsf@orcus.priv.at \
--to=robbe@orcus.priv.at \
--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.