From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] More work on policy_components.c
Date: Thu, 20 Oct 2005 13:30:55 -0400 [thread overview]
Message-ID: <4357D44F.5080000@cornell.edu> (raw)
In-Reply-To: <1129828287.2375.435.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2005-10-20 at 13:21 -0400, Ivan Gyurdiev wrote:
>
>> The problem is from earlier patches - you can comment out the init() and
>> release() code in direct_api.c - should eliminate any bugs. I didn't
>> think something as simple would be broken. I'll fix the problem a bit
>> later today...
>>
>
> I think that this may help...
>
doh...
Like I was saying :)
With that last patch I just sent, I can begin to test functionality, add
error messages, fix bugs, and implement stubs.
The first thing I need to do is to figure out whether my
dbase_policydb_cache function will work on policy.kern (but this is
challenging, as I can't seem to get a policy.kern in the first place -
commit keeps failing, and it's definitely not my fault that it does so...).
I should also focus a bit on sepol, where the interfaces need to be
stabilized...
--
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-10-20 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 1:24 [ SEMANAGE ] More work on policy_components.c Ivan Gyurdiev
2005-10-20 15:05 ` Stephen Smalley
2005-10-20 17:12 ` [ SEMANAGE ] More dbase things Ivan Gyurdiev
2005-10-20 17:58 ` Stephen Smalley
2005-10-20 16:55 ` [ SEMANAGE ] More work on policy_components.c Stephen Smalley
2005-10-20 17:04 ` Stephen Smalley
2005-10-20 17:21 ` Ivan Gyurdiev
2005-10-20 17:11 ` Stephen Smalley
2005-10-20 17:16 ` Stephen Smalley
2005-10-20 17:30 ` Ivan Gyurdiev [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=4357D44F.5080000@cornell.edu \
--to=ivg2@cornell.edu \
--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.