From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>,
selinux@tycho.nsa.gov, Joshua Brindle <jbrindle@tresys.com>,
Karl MacMillan <kmacmillan@tresys.com>,
Frank Mayer <mayerf@tresys.com>,
chris pebenito <cpebenito@tresys.com>,
James Morris <jmorris@redhat.com>,
Chad Sellers <csellers@tresys.com>
Subject: Re: [ SELINUX ] [ POLICYCOREUTILS ] Convert setsebool -P to use libsemanage
Date: Fri, 04 Nov 2005 11:05:50 -0500 [thread overview]
Message-ID: <436B86DE.4090207@redhat.com> (raw)
In-Reply-To: <1131118753.23420.270.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Fri, 2005-11-04 at 00:55 -0500, Ivan Gyurdiev wrote:
>
>> - always return -1 on failure. I highly dislike any creativity with the
>> return value.
>>
>
> Hmmm...so the 'ret' value is now unused, but those error codes were
> being propagated all the way up to the exit status of the program. So
> this constitutes an "interface change". Question is whether any caller
> was using those individual ret values for any purpose - Dan? Does
> system-config-securitylevel distinguish error codes from setsebool?
>
>
Nope it is ignored.
--
--
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.
prev parent reply other threads:[~2005-11-04 16:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436915FB.3040500@tresys.com>
[not found] ` <1131027033.23420.30.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <436A86E6.4040205@cornell.edu>
2005-11-04 5:55 ` [ SELINUX ] [ POLICYCOREUTILS ] Convert setsebool -P to use libsemanage Ivan Gyurdiev
2005-11-04 13:20 ` Stephen Smalley
2005-11-04 14:22 ` Ivan Gyurdiev
2005-11-04 14:16 ` Stephen Smalley
2005-11-05 7:06 ` [ LIBSEMANAGE ] Runtime control over preservebools argument Ivan Gyurdiev
2005-11-07 14:38 ` Joshua Brindle
2005-11-07 15:12 ` Daniel J Walsh
2005-11-04 14:57 ` [ SELINUX ] [ POLICYCOREUTILS ] Convert setsebool -P to use libsemanage Stephen Smalley
2005-11-04 15:35 ` Ivan Gyurdiev
2005-11-04 14:59 ` Stephen Smalley
2005-11-04 15:43 ` Ivan Gyurdiev
2005-11-04 15:33 ` Stephen Smalley
2005-11-04 16:08 ` Daniel J Walsh
2005-11-04 16:12 ` Stephen Smalley
2005-11-04 16:31 ` Stephen Smalley
2005-11-04 17:08 ` Ivan Gyurdiev
2005-11-04 16:59 ` Stephen Smalley
2005-11-04 17:04 ` Stephen Smalley
2005-11-04 17:11 ` Stephen Smalley
2005-11-04 21:54 ` Ivan Gyurdiev
2005-11-04 21:59 ` Ivan Gyurdiev
2005-11-07 13:48 ` Stephen Smalley
2005-11-07 14:56 ` Stephen Smalley
2005-11-07 15:09 ` Stephen Smalley
2005-11-07 16:40 ` Ivan Gyurdiev
2005-11-07 16:33 ` Stephen Smalley
2005-11-04 15:39 ` Stephen Smalley
2005-11-04 16:05 ` Daniel J Walsh [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=436B86DE.4090207@redhat.com \
--to=dwalsh@redhat.com \
--cc=cpebenito@tresys.com \
--cc=csellers@tresys.com \
--cc=ivg2@cornell.edu \
--cc=jbrindle@tresys.com \
--cc=jmorris@redhat.com \
--cc=kmacmillan@tresys.com \
--cc=mayerf@tresys.com \
--cc=sds@epoch.ncsc.mil \
--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.