All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Warner <warner@rubix.com>
To: Vesa-Matti J Kari <vmkari@cc.helsinki.fi>
Cc: russell@coker.com.au, Casey Schaufler <casey@schaufler-ca.com>,
	SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: Request for multiple mailing lists
Date: Fri, 08 Aug 2008 12:10:57 +0200	[thread overview]
Message-ID: <489C1BB1.2060701@rubix.com> (raw)
In-Reply-To: <Pine.LNX.4.64L.0808081256260.24072@ruuvi.it.helsinki.fi>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]



Vesa-Matti J Kari wrote:
> Hello,
>
> On Fri, 8 Aug 2008, Andy Warner wrote:
>
>   
>> Russell Coker wrote:
>>     
>>> On Friday 08 August 2008 03:47, Casey Schaufler <casey@schaufler-ca.com>
>>> wrote:
>>>
>>>       
>>>> SELinux without policy is like a book without pages. Think of
>>>> the reference policy as the pages of the Old Testament.
>>>>
>>>>         
>>> http://en.wikipedia.org/wiki/Eisegesis
>>>
>>> The problem with such analogies is that SE Linux policy is designed to be
>>> unambiguous.  See the above URL for details of the issue.
>>>
>>>
>>>       
>> Is that supposed to be funny or just an great example of someone posting way
>> off topic demonstrating the need for multiple mailing lists?
>>     
>
> There is nothing inherently funny with being logical and demanding
> precision. Russell Coker's comment was quite good and to the point. You
> should not compare SELinux policies, which are clear and precise, with
> ancient mythology, and expect that everyone buys it. This world is full
> of so-called Holy Books, after all.
>
> This list should focus on SELinux issues.
>
> Best regards,
> vmk
>   
Didn't realize the NSA was sponsoring a list for voicing religious 
bigotries. Or is that also an "SELinux issue?"

[-- Attachment #2: Type: text/html, Size: 1954 bytes --]

  reply	other threads:[~2008-08-08 10:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 16:41 Request for multiple mailing lists Vikram Ambrose
2008-08-07 17:47 ` Casey Schaufler
2008-08-07 18:55   ` Stanley A. Klein
2008-08-08  2:08   ` Russell Coker
2008-08-08  3:18     ` Casey Schaufler
2008-08-08  8:29     ` Andy Warner
2008-08-08 10:01       ` Vesa-Matti J Kari
2008-08-08 10:10         ` Andy Warner [this message]
2008-08-08 10:33           ` Vesa-Matti J Kari
2008-08-08 10:48             ` Russell Coker
2008-08-08 17:10               ` Joshua Brindle
2008-08-09  2:20                 ` max bianco
2008-08-09  2:45                   ` Russell Coker
2008-08-14 16:16                 ` Stephen Smalley
2008-08-15  5:18                   ` Russell Coker
2008-08-09  2:27               ` Casey Schaufler
2008-08-11 14:20 ` Vikram Ambrose
2008-08-11 15:34 ` Eric Paris
2008-08-11 17:17   ` Justin Mattock

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=489C1BB1.2060701@rubix.com \
    --to=warner@rubix.com \
    --cc=casey@schaufler-ca.com \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    --cc=vmkari@cc.helsinki.fi \
    /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.