Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: KDE 4.1.2 issues - updated
Date: Tue, 04 Nov 2008 23:14:52
Message-Id: pan.2008.11.04.23.14.33@cox.net
In Reply to: Re: [gentoo-amd64] KDE 4.1.2 issues - updated by Beso
1 Beso <givemesugarr@×××××.com> posted
2 d257c3560811041417h16cfc3bby1eed7cb0e4b002ef@××××××××××.com, excerpted
3 below, on Tue, 04 Nov 2008 22:17:09 +0000:
4
5 >> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in
6 >> /etc/X11/Sessions/
7
8 FWIW, I don't use a *dm at all. I boot to a virtual terminal in text
9 mode, login there, and start X/KDE from there. The /etc/X11/Sessions/*
10 entries are for doing that. You set and export XSESSION=<name>, where
11 <name> is the name of one of those files, run startx, and it should do
12 just that (start X), with the appropriate environment based on whichever
13 one you set/exported, logged in as the user you ran startx as. Note that
14 formerly the XSESSION variable was set system-wide in some rc file, IDR
15 which but something like /etc/conf.d/rc or some such, but at least with
16 baselayout-2 and openrc, that's no longer the case. Individual logins
17 could always overrule it; now they set it, period, in their bashrc or
18 individual scripts they create or whatever.
19
20 Of course the KDE X11/Sessions files don't do much, only call startkde
21 (of the appropriate version) at the appropriate time as X starts. It's
22 the startkde scripts that do the real work.
23
24 But since I've customized the locations of a number of files, due to
25 running /tmp on tmpfs and /var/tmp as a symlink pointed at it, plus
26 customized the menu and etc for both kde3 and kde4, I have customized KDE
27 start scripts as well. These set various critical variables to point
28 stuff at my customized locations, do a few more symlinks beyond what
29 startkde does to keep the kde3 and kde4 user configs from stepping on
30 each other, etc.
31
32 But the point is, no dm is necessary. KDE (or other environments as
33 merged) can be started from the console login, provided (1) XSESSION is
34 set correctly, and (2) the appropriate start scripts, for kde, the
35 startkde package, is merged. I have both the 3.5.10-r4 and 4.1.2-r1
36 versions of kdebase-startkde merged, and can start either one from my
37 virtual terminal login.
38
39 > as displaymanager i have just 4.0 (i should correct it to the newer one
40 > but it seems that for me it automatically detects changes). usually this
41 > shouldn't be necessary as the new /etc/init.d/xdm file should already
42 > point to the right location (i have different voices for kde3.5 kde4 and
43 > gnome that go and see the kdm in the {MY_KDE} directory under /usr/kde/.
44 > so if you have a look at that the DISPLAYMANAGER should point just to
45 > the right dir. if you have /usr/kde/4.1 point it to 4.1. also you should
46 > remember to install the kdebase-startkde-4.1.2 package or you won't be
47 > able to select that session.
48
49 Now, if you are running a display manager, with a graphical login, then
50 the above applies. However, it's not necessary, and I long ago (2003-
51 ish, Mandrake 8.x) quit doing so, after Mandrake broke their DM login in
52 whatever cooker version I was running at the time. IIRC I had already
53 been running KDE from text mode part of the time (having decided before
54 that that I preferred KDE to GNOME or whatever), but after that, I got in
55 the habit of doing it all the time, and I've never used whatever *DM at
56 all on Gentoo, and haven't even had one merged since Gentoo/KDE started
57 the split packages thing. I just prefer logging in in text mode, I
58 guess, and running X/KDE like I would any other application, from there.
59
60 --
61 Duncan - List replies preferred. No HTML msgs.
62 "Every nonfree program has a lord, a master --
63 and if you use the program, he is your master." Richard Stallman