All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>,
	Karl MacMillan <kmacmillan@tresys.com>
Subject: Re: [ SEPOL ] Another debugging system
Date: Tue, 11 Oct 2005 11:11:55 -0400	[thread overview]
Message-ID: <434BD63B.7020003@cornell.edu> (raw)
In-Reply-To: <1129041930.3308.137.camel@moss-spartans.epoch.ncsc.mil>


> - Same comments apply as for the semanage patch.
>   
Allright, I'll redo both of those patches for tomorrow (no time today).
Thanks for the comments.
> - Yes, sepol.h should likely include all external API sepol headers, and
> the current interfaces in sepol.h should likely be moved to separate
> headers that are then included.
>   
Will change that in a later patch..

> - We'll need to preserve versions of the old sepol.h interfaces without
> handles for backward compatibility, since there have been official
> releases with those interfaces.  Some of those interfaces will be
> obsoleted (genusers/genbools) but others will continue to be used
> (genbools_array for load_policy, set_policydb_from_file and
> check_context for setfiles -c).
>   
I'm confused - what's the difference between an "old" interface that has 
a corresponding "new" interface... and an obsoleted interface. Seems 
like the same thing to me. Yes, we'll need need to preserve 
compatibility until all users are fixed, and then we can get rid of the 
old interfaces..right?


--
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.

  reply	other threads:[~2005-10-11 15:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-11  6:59 [ SEMANAGE ] Replace semanage debugging system Ivan Gyurdiev
2005-10-11  9:03 ` [ SEPOL ] Another " Ivan Gyurdiev
2005-10-11 14:45   ` Stephen Smalley
2005-10-11 15:11     ` Ivan Gyurdiev [this message]
2005-10-11 15:15       ` Stephen Smalley
2005-10-11 15:51         ` Stephen Smalley
2005-10-11 13:34 ` [ SEMANAGE ] Replace semanage " Stephen Smalley
2005-10-11 14:06   ` Stephen Smalley
2005-10-11 14:29     ` Ivan Gyurdiev
2005-10-11 14:30       ` Stephen Smalley
2005-10-11 14:57         ` Ivan Gyurdiev
2005-10-11 14:46           ` Stephen Smalley
2005-10-11 15:18             ` Ivan Gyurdiev
2005-10-11 15:19               ` Stephen Smalley
2005-10-11 16:35                 ` Ivan Gyurdiev
2005-10-11 17:27           ` Ivan Gyurdiev
2005-10-11 17:23             ` Stephen Smalley
2005-10-11 14:15   ` Ivan Gyurdiev
2005-10-11 14:24     ` Stephen Smalley

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=434BD63B.7020003@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=dwalsh@redhat.com \
    --cc=kmacmillan@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --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.