From: Daniel J Walsh <dwalsh@redhat.com>
To: russell@coker.com.au
Cc: janak@us.ibm.com, "Timothy R. Chavez" <tinytim@us.ibm.com>,
sgrubb@redhat.com, tmraz@redhat.com, klaus@atsec.com,
Valdis.Kletnieks@vt.edu, sds@tycho.nsa.gov,
selinux@tycho.nsa.gov
Subject: Re: [PATCH] pam_namespace : allow use of X and gdm while polyinstantiating /tmp
Date: Sat, 17 Jun 2006 06:33:04 -0400 [thread overview]
Message-ID: <4493DA60.8010801@redhat.com> (raw)
In-Reply-To: <200606172027.51997.russell@coker.com.au>
Russell Coker wrote:
> On Saturday 17 June 2006 19:52, Daniel J Walsh <dwalsh@redhat.com> wrote:
>
>>> What exactly do you mean? Do you mean moving it somewhere else such
>>> as /var/run or do you mean using TCP instead?
>>>
>> They are talking about using abstract namespaces.
>>
>
> What exactly do you mean? Do you mean having the X server or the XDM program
> create PI directories?
>
>
That is all I know.
They are looking at having the XServer listen on abstract sockets.
I think Bill Crawford (OgreBoy) wrote a patch to do this and they are
investigating it.
Nothing may come of this, but they are considering it.
--
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.
next prev parent reply other threads:[~2006-06-17 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 2:56 [PATCH] pam_namespace : allow use of X and gdm while polyinstantiating /tmp Janak Desai
2006-06-16 17:38 ` Timothy R. Chavez
2006-06-16 17:51 ` Janak Desai
2006-06-16 18:35 ` Daniel J Walsh
2006-06-16 19:57 ` Casey Schaufler
2006-06-17 0:30 ` Russell Coker
2006-06-17 9:52 ` Daniel J Walsh
2006-06-17 10:27 ` Russell Coker
2006-06-17 10:33 ` Daniel J Walsh [this message]
2006-06-18 18:51 ` James Antill
2006-06-19 0:01 ` Janak Desai
2006-06-17 2:24 ` Valdis.Kletnieks
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=4493DA60.8010801@redhat.com \
--to=dwalsh@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=janak@us.ibm.com \
--cc=klaus@atsec.com \
--cc=russell@coker.com.au \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=sgrubb@redhat.com \
--cc=tinytim@us.ibm.com \
--cc=tmraz@redhat.com \
/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.