All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: Russell Coker <russell@coker.com.au>
Cc: selinux@tycho.nsa.gov
Subject: Re: xdm (not kdm) policy ?
Date: Tue, 20 May 2003 17:49:21 +0200	[thread overview]
Message-ID: <20030520174914.A10662@lemuria.org> (raw)
In-Reply-To: <200305210015.37136.russell@coker.com.au>; from russell@coker.com.au on Wed, May 21, 2003 at 12:15:37AM +1000

On Wed, May 21, 2003 at 12:15:37AM +1000, Russell Coker wrote:
> My patch for kdm 2.2 is still online.
> 
> I've attached the latest patch I was playing with for kdm 3.1.x.  I never 
> tested this one because I never could get kdm to compile.

I played with these yesterday, for several hours. Now I hate KDE (or
rather: it's build process - have they never heard of modularization?), but
I still have no working kdm. :)


I'm currently working on patching wdm. The necessary changes seem to be
easy enough to make. And since it uses autoconf, I'll try submitting it
to the upstream author once it works.

One question, though: wdm uses system() calls for reboot and halt. How
should I deal with those?


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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:[~2003-05-20 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 12:51 xdm (not kdm) policy ? Tom
2003-05-20 14:15 ` Russell Coker
2003-05-20 15:49   ` Tom [this message]
2003-05-20 17:15   ` Tom
2003-05-20 18:04   ` Torsten Knodt

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=20030520174914.A10662@lemuria.org \
    --to=tom@lemuria.org \
    --cc=russell@coker.com.au \
    --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.