From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Feckless xdm not much of a manager
Date: Wed, 25 Aug 2010 15:28:25 +0100 [thread overview]
Message-ID: <AANLkTi=nTZzN53nmtEyFBPx=HcGaC=L81q7B2fF99gM8@mail.gmail.com> (raw)
In-Reply-To: <4C75270A.3090909@gmail.com>
On 25 August 2010 15:22, Bill Longman <bill.longman@gmail.com> wrote:
> On 08/24/2010 08:36 PM, Kevin O'Gorman wrote:
>> 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.
>
> You ~should~ be able to log onto a console vty by using Ctrl-Alt-Fn
> (where n=1-6). You can then log on from there and commence all manner of
> Gentacular shelly goodness.
>
> There's really no need to kill the display manager ever. In fact, you
> can have more than one running at a time.
>
>> 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.
>
> Yeah, that's just a semantic problem, really. The generic term is "xdm"
> but depending upon your setup, you can plug in any display manager.
Running /etc/init.d/xdm stop should kill kdm too. If it respawns,
then run /etc/init.d/xdm zap.
--
Regards,
Mick
next prev parent reply other threads:[~2010-08-25 14:28 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 ` [gentoo-user] " Kevin O'Gorman
2010-08-25 14:22 ` [gentoo-user] " Bill Longman
2010-08-25 14:28 ` Mick [this message]
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='AANLkTi=nTZzN53nmtEyFBPx=HcGaC=L81q7B2fF99gM8@mail.gmail.com' \
--to=michaelkintzios@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