All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: selinux <selinux@tycho.nsa.gov>, selinux-dev@tresys.com
Subject: Re: [RFC] Module language syntax
Date: Fri, 27 May 2005 21:05:40 +0100	[thread overview]
Message-ID: <20050527200540.GC1544@lkcl.net> (raw)
In-Reply-To: <1117220066.9783.27.camel@localhost>

On Fri, May 27, 2005 at 02:54:26PM -0400, Joshua Brindle wrote:
> On Fri, 2005-05-27 at 19:53 +0100, Luke Kenneth Casson Leighton wrote:
> > On Fri, May 27, 2005 at 02:17:33PM -0400, Joshua Brindle wrote:
> > 
> > > installation. The production environment then does not need a build
> > > environment such as make, m4 and so on. The module tools will allow
> > > these modules to be "linked in" to the current policy. It's at this link
> > > time that both the modules dependencies and the optional dependencies
> > > are determined and optionals with fulfilled dependencies are enabled.
> >  
> >  i take it that booleans are ... just... added / supported, too?
> > 
> >  such that they are declared in the binary module, used in the binary
> >  module, added to the config files and can be set at runtime, yes/
> > 
> >  l.
> > 
> 
> booleans and conditionals are runtime and are not at all affected by the
> loadable modules. 


 great!  ... just checkin :)


--
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-05-27 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 18:17 [RFC] Module language syntax Joshua Brindle
2005-05-27 18:53 ` Luke Kenneth Casson Leighton
2005-05-27 18:54   ` Joshua Brindle
2005-05-27 20:05     ` Luke Kenneth Casson Leighton [this message]
2005-06-14  5:12     ` Russell Coker
2005-06-14 12:20       ` Joshua Brindle

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=20050527200540.GC1544@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=jbrindle@tresys.com \
    --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.