From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Feckless xdm not much of a manager
Date: Tue, 24 Aug 2010 20:55:41 -0700 [thread overview]
Message-ID: <AANLkTinpULhSJ85z4GEmPXBi2p0QbMnoOyirRW97Bfvj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTineoO-pCd-euV4BqvnRmuqq-n5dBcV5yJUjLTrX@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Tue, Aug 24, 2010 at 8:36 PM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> I'm actually working to integrate a new HD monitor in a system built before
> HD was invented. The monitor works better than the old one, but just in 4:3
> aspect mode. But that's another thread, I only mention it so you know I'm
> as well off as I was before the old monitor fritzed out on me.
>
> In order to make progress on this thing, it's useful to be able to control
> the display manager. My problem has been that going to /etc/init.d
> and commanding "./xdm stop" seems to work, but has no effect on KDE.
> Manually killing kde (ps -ef | grep kde, etc) just starts another one. I
> finally figured out that I have to find the 'kdm' process and kill that,
> then a logoff or Ctl_Alt_BS actually gets rid of X, so I can do things like
> "X -configure" and so on.
>
> Oddly, "./xdm start" worked fine, and was responsible for kdm being
> started. But isn't it odd that the display "manager" has such weak
> control on its "subordinate"? Big PITA for me.
>
> Grrrrr.
>
>
The reason that some of this was in the past tense is that somehow I've
gotten in a situation
where rebooting does _not_ start a display manager. Fortunately, "./xdm
start" still works --
it's just more PITA..
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 1738 bytes --]
next prev parent reply other threads:[~2010-08-25 3:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 3:36 [gentoo-user] Feckless xdm not much of a manager Kevin O'Gorman
2010-08-25 3:55 ` Kevin O'Gorman [this message]
2010-08-25 14:22 ` Bill Longman
2010-08-25 14:28 ` Mick
2010-08-25 19:37 ` Kevin O'Gorman
2010-08-25 19:44 ` Alex Schuster
2010-08-26 1:53 ` Michael Orlitzky
2010-08-25 19:33 ` Kevin O'Gorman
2010-08-25 20:40 ` Robert Bridge
2010-08-26 15:34 ` Bill Longman
2010-08-25 23:00 ` Stroller
2010-08-26 19:07 ` Kevin O'Gorman
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=AANLkTinpULhSJ85z4GEmPXBi2p0QbMnoOyirRW97Bfvj@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox