All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: jwcart2@tycho.nsa.gov
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: Last attempt at upstreaming semodule_disable patch.
Date: Wed, 24 Feb 2010 15:23:58 -0500	[thread overview]
Message-ID: <4B858ADE.6000704@redhat.com> (raw)
In-Reply-To: <1267042349.2051.14.camel@localhost>

On 02/24/2010 03:12 PM, James Carter wrote:
> On Wed, 2010-02-24 at 14:50 -0500, Daniel J Walsh wrote:
>    
>> This patch allows you to disable/Enable policy modules.
>>
>> It never seems to get upstreamed.  :^(
>>      
> Caleb's patch set in December not only moves the policy store and adds
> priority support, it also allows modules to be enabled and disabled.
>
> The hope is that that patch set as well as the one adding support for
> source policy modules can be upstreamed sometime in the near future.
>
>    
Yes I look forward to that patch but that is not going to be used until 
Fedora 14 at the earliest.  Anyone distros working off the current code, 
could use this patch.   But if it is not wanted, I can leave it as a 
patch for the next 7 years.  :^)



--
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:[~2010-02-24 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 19:50 Last attempt at upstreaming semodule_disable patch Daniel J Walsh
2010-02-24 20:03 ` Dominick Grift
2010-02-24 20:12 ` James Carter
2010-02-24 20:23   ` Daniel J Walsh [this message]
2010-02-26  1:43   ` Joshua Brindle
2010-03-06 22:50 ` Joshua Brindle
2010-03-06 23:12   ` 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=4B858ADE.6000704@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=jwcart2@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.