All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Chad Sellers <csellers@tresys.com>
Cc: Caleb Case <ccase@tresys.com>, SE Linux <selinux@tycho.nsa.gov>,
	"Christopher J. PeBenito" <cpebenito@tresys.com>,
	Joshua Brindle <method@manicmethod.com>
Subject: Re: SELinux context patch
Date: Thu, 04 Jun 2009 17:07:26 -0400	[thread overview]
Message-ID: <4A28378E.2000609@redhat.com> (raw)
In-Reply-To: <C64DAB34.A7B1B%csellers@tresys.com>

On 06/04/2009 04:47 PM, Chad Sellers wrote:
> On 6/4/09 3:13 PM, "Caleb Case"<ccase@tresys.com>  wrote:
>>
>> I don't think it will adversely affect FCGlob integration.
>>
> Very good.
>
> <snip>
>>
>> It doesn't support directories with spaces in them.
>
> An excellent point, though it looks like file_contexts doesn't support
> spaces right now either.
>
> Thanks,
> Chad
>
>
> --
> 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.
Directories with spaces, are satanic.

Just say no to spaces in Directory names.

--
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:[~2009-06-04 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 18:16 SELinux context patch Daniel J Walsh
2009-05-20 16:08 ` Chad Sellers
2009-06-04 19:13   ` Caleb Case
2009-06-04 20:47     ` Chad Sellers
2009-06-04 21:07       ` Daniel J Walsh [this message]
2009-06-04 21:15     ` Daniel J Walsh
2009-06-05 17:12     ` Christopher J. PeBenito
2009-06-05 17:24       ` Christopher J. PeBenito
2009-06-04 21:14 ` Chad Sellers
2009-06-23 17:10   ` 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=4A28378E.2000609@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=ccase@tresys.com \
    --cc=cpebenito@tresys.com \
    --cc=csellers@tresys.com \
    --cc=method@manicmethod.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.