From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is rc.conf no longer used by Gentoo (baselayout-1.12.13)?
Date: Sun, 13 Dec 2009 20:43:41 +0000 [thread overview]
Message-ID: <200912132044.00264.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4B254CEB.80808@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2090 bytes --]
On Sunday 13 December 2009 20:22:03 Dale wrote:
> Mick wrote:
> > Hi All,
> >
> > I got mixed up with the various .fdi files in a previous thread, thinking
> > that this is what killed my X GUI. However, it seems that the problem is
> > most likely related to rc.conf. Has this file been done away with as far
> > as Gentoo is concerned? I say this because I discovered that running
> > dispatch.conf after sys-apps/baselayout-1.12.13 substitutes /etc/rc.conf
> > with an empty file. Mind you, even if the file contains the previous
> > information about XSESSION xdm or slim do not seem to use it now.
> >
> > If this is the case, am I right to assume that the files in
> > /etc/X11/Sessions/* are not used anymore and the solution is to set up a
> > local ~/.xinitrc file for launching the desired WM?
> >
> > I am muddled up because I have forever it seems used /etc/rc.conf to
> > manage the XSESSION which xdm would pick from /etc/X11/Sessions/* to
> > start different WMs.
> >
> > Right now I have copied the contents of /etc/X11/Sessions/fluxbox into
> > ~/.xinitrc, added slim's /usr/share/doc/slim-1.3.1-r4/xinitrc.sample.bz2
> > and that's how I can get fluxbox to come up.
> >
> > What is the default Gentoo way these days of bringing up an X session?
> >
> > PS. Is there a clever way of killing slim? It seems that
> > /etc/init.d/xdm stop/zap won't kill slim or the X session that it starts.
> > I need to manually run kill -9 to make it give up.
>
> Well, I'm a KDE guy myself so this may just be completely wrong here. I
> put my X stuff in /etc/conf.d/xdm and it tells what I am using for my
> GUI. Again, I don't have Fluxbox and I understand it works differently
> so this may be as far off as Pluto.
Thanks Dale,
The /etc/conf.d/xdm file, which arrived after the /etc/rc.conf days, is indeed
used to set up the Display Manager, but not the Window Manager/Display
Environment X session. The latter was being defined in rc.conf, but this I
think is no longer the case - hence I am asking here.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-13 20:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 18:30 [gentoo-user] Is rc.conf no longer used by Gentoo (baselayout-1.12.13)? Mick
2009-12-13 20:22 ` Dale
2009-12-13 20:43 ` Mick [this message]
2009-12-13 22:14 ` Dale
2009-12-13 23:01 ` Neil Bothwick
2009-12-14 11:18 ` Mick
2009-12-14 12:22 ` Neil Bothwick
2009-12-14 17:00 ` Allan Gottlieb
2009-12-14 21:55 ` pk
2009-12-14 22:43 ` Allan Gottlieb
2009-12-16 19:16 ` pk
2009-12-17 3:54 ` Allan Gottlieb
2009-12-14 20:50 ` Mick
2009-12-14 22:45 ` Mike Edenfield
2009-12-14 23:02 ` Mick
2009-12-13 22:02 ` Mike Mazur
2009-12-14 11:17 ` Mick
2009-12-14 11:31 ` Mike Mazur
2009-12-14 12:22 ` Patrick Holthaus
2009-12-15 5:29 ` daid kahl
2009-12-15 15:38 ` Marcus Wanner
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=200912132044.00264.michaelkintzios@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