On 2012/06/27 10:58 (GMT+0200) Stefan Dirsch composed:

On Tue, Jun 26, 2012 at 05:27:07AM -0400, Felix Miata wrote:

 >>  Why on a system with kdm already installed are twm and xdm required?

 >xdm scripts are used by kdm

 Is this an upstream "feature"?

This is a framework developped and well maintained by SUSE and used by
xdm/kdm/gdm on our distribution since a long time now. Are you interested in
replacing it with something different?

No. It just seems that GDM & KDM upstream would have competent configurations to not depend on other dms, leaving me puzzled as to what value(s) openSUSE personalization in this area might be.

 >twm is still used as a fallback by the xdm init script.

 That I have noticed on occasion, and usually find that it starts
 instead of a KDE session (that won't start because something's
 broken or missing) annoying.

Still better than no WM at all IMO.

I see that microfont message box sometimes, and wonder what it expects me to do next after I find my magnifying glass to read it, whereas if no WM started, I'd focus right in on finding out why.

 Meanwhile I have one B2 system on which "init 5/telinit 5" instantly
 returns zilch and no new Xorg.0.log, while startx works fine. I may
 just make that my next target of a fresh install instead of trying
 to figure out why. :-p

Well, I didn't manage to install openSUSE 12.2 Beta2 at all so far, so you're
already *steps* further than me. ;-)

I've installed several times since 12.2's YaST broke[1], including just minutes ago from factory-snapshot. I just don't use YaST for packaging activities, starting installation with just a minimal X or server install and then zypper on first and subsequent 12.2 boots.

[1] https://bugzilla.novell.com/show_bug.cgi?id=765769
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to