From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Joshua Brindle <jbrindle@tresys.com>,
selinux@tycho.nsa.gov, Russell Coker <russell@coker.com.au>,
selinux-dev@tresys.com
Subject: Re: Now that SELinux supports booleans should we replace tunables with booleans?
Date: Fri, 06 Aug 2004 10:38:01 -0400 [thread overview]
Message-ID: <411397C9.2010606@redhat.com> (raw)
In-Reply-To: <1091802482.8590.62.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Fri, 2004-08-06 at 10:20, Joshua Brindle wrote:
>
>
>>If they are going to be changed they should probably also be changed to
>>match the get/set convention used by most other selinux apps.
>>
>>
>
>I can see renaming change_bool to setsebool or something similar, and
>adding a new getsebool <boolean> that just displays the value of the
>specified boolean. show_bools is a little different in that it shows
>all booleans and their values, so possibly listsebools. toggle_sebool
>has no equivalent.
>
>
show_bools should be getseboo -a.
Dan
--
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:[~2004-08-06 14:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 13:59 Now that SELinux supports booleans should we replace tunables with booleans? Daniel J Walsh
2004-04-13 17:09 ` Chris PeBenito
2004-04-13 17:53 ` Tom Mitchell
2004-04-14 13:16 ` Karl MacMillan
2004-04-14 16:19 ` Russell Coker
2004-04-14 17:19 ` Karl MacMillan
2004-04-14 19:50 ` Valdis.Kletnieks
[not found] ` <407DF398.4010405@redhat.com>
2004-04-15 5:28 ` Russell Coker
2004-04-15 14:52 ` Valdis.Kletnieks
2004-04-14 19:58 ` James Morris
2004-04-14 20:19 ` James Morris
2004-04-21 16:05 ` Karl MacMillan
2004-04-13 23:17 ` Russell Coker
2004-04-14 13:11 ` Karl MacMillan
2004-04-14 13:30 ` Stephen Smalley
2004-04-14 14:10 ` Now that SELinux supports booleans should we replace tunableswith booleans? Karl MacMillan
2004-04-14 16:00 ` Russell Coker
2004-04-14 13:38 ` Now that SELinux supports booleans should we replace tunables with booleans? Russell Coker
2004-04-14 14:53 ` Karl MacMillan
2004-08-02 18:53 ` Stephen Smalley
2004-08-02 19:08 ` Stephen Smalley
2004-08-05 12:30 ` Stephen Smalley
2004-08-05 12:33 ` Stephen Smalley
2004-08-05 13:44 ` Daniel J Walsh
2004-08-06 14:04 ` Stephen Smalley
2004-08-06 15:57 ` Now that SELinux supports booleans should we replace tunableswith booleans? Karl MacMillan
2004-08-06 16:20 ` Stephen Smalley
2004-08-09 20:11 ` Stephen Smalley
2004-08-10 6:46 ` Russell Coker
2004-08-10 14:29 ` Karl MacMillan
2004-08-10 14:33 ` Daniel J Walsh
2004-08-10 14:47 ` Karl MacMillan
2004-08-10 14:43 ` Stephen Smalley
2004-08-10 17:06 ` Timothy Wood
2004-08-10 17:20 ` Stephen Smalley
2004-08-10 13:25 ` Daniel J Walsh
2004-08-06 14:02 ` Now that SELinux supports booleans should we replace tunables with booleans? Stephen Smalley
2004-08-06 14:20 ` Joshua Brindle
2004-08-06 14:28 ` Stephen Smalley
2004-08-06 14:38 ` Daniel J Walsh [this message]
2004-08-06 15:30 ` Stephen Smalley
2004-08-06 15:36 ` kmacmillan
2004-08-06 14:23 ` Stephen Smalley
2004-08-06 14:40 ` Daniel J Walsh
2004-08-06 15:02 ` Stephen Smalley
2004-08-23 19:33 ` 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=411397C9.2010606@redhat.com \
--to=dwalsh@redhat.com \
--cc=jbrindle@tresys.com \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--cc=selinux-dev@tresys.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.