1 |
Mick wrote: |
2 |
> Hi All, |
3 |
> |
4 |
> I got mixed up with the various .fdi files in a previous thread, thinking that |
5 |
> this is what killed my X GUI. However, it seems that the problem is most |
6 |
> likely related to rc.conf. Has this file been done away with as far as Gentoo |
7 |
> is concerned? I say this because I discovered that running dispatch.conf |
8 |
> after sys-apps/baselayout-1.12.13 substitutes /etc/rc.conf with an empty file. |
9 |
> Mind you, even if the file contains the previous information about XSESSION |
10 |
> xdm or slim do not seem to use it now. |
11 |
> |
12 |
> If this is the case, am I right to assume that the files in |
13 |
> /etc/X11/Sessions/* are not used anymore and the solution is to set up a local |
14 |
> ~/.xinitrc file for launching the desired WM? |
15 |
> |
16 |
> I am muddled up because I have forever it seems used /etc/rc.conf to manage |
17 |
> the XSESSION which xdm would pick from /etc/X11/Sessions/* to start different |
18 |
> WMs. |
19 |
> |
20 |
> Right now I have copied the contents of /etc/X11/Sessions/fluxbox into |
21 |
> ~/.xinitrc, added slim's /usr/share/doc/slim-1.3.1-r4/xinitrc.sample.bz2 and |
22 |
> that's how I can get fluxbox to come up. |
23 |
> |
24 |
> What is the default Gentoo way these days of bringing up an X session? |
25 |
> |
26 |
> PS. Is there a clever way of killing slim? It seems that /etc/init.d/xdm |
27 |
> stop/zap won't kill slim or the X session that it starts. I need to manually |
28 |
> run kill -9 to make it give up. |
29 |
> |
30 |
|
31 |
Well, I'm a KDE guy myself so this may just be completely wrong here. I |
32 |
put my X stuff in /etc/conf.d/xdm and it tells what I am using for my |
33 |
GUI. Again, I don't have Fluxbox and I understand it works differently |
34 |
so this may be as far off as Pluto. |
35 |
|
36 |
Dale |
37 |
|
38 |
:-) :-) |