From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re: Re: Re: livecd-stage1 pkgconfig
Date: Tue, 12 Jul 2005 14:05:05 -0400 [thread overview]
Message-ID: <1121191505.11002.46.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <pan.2005.07.12.17.26.45.618195@novazur.fr>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
On Tue, 2005-07-12 at 13:26 -0400, Christophe PEREZ wrote:
> Le Tue, 12 Jul 2005 13:01:31 -0400, Chris Gianelloni a écrit :
>
> >> Use of xinitrc could be better, isn't it ?
> >> And xinitrc could permit to adapt better the X start for something more
> >> complicated than just a "su - user -c startx".
> >> If I want to use it, what service will be started by ?
> >
> > Umm... You're supposed to use both.
>
> Yes, but I didn't explained very well.
> I mean there are 2 way :
> - catalyst xinitrc (never used it)
> - root/.bashrc
>
> no ?
No. A xinitrc file is what is executed when you run "startx" from the
command line.
> > livecd/xinitrc:
>
> Yes, but I don't know what service excute xinitrc. xdm ?
> In fact, I want one user created, X started by this user at boot without
> session manager (xdm, kdm, gdm).
The xinitrc has nothing to do with any session management or display
management, but rather when calling startx.
> >> I added alsa in my kernel, alsa-utils in packages, and alsa-sound at boot..
> >
> > You probably want alsasound to start after coldplug.
>
> So I have to manually (ffscript) modify alsa-sound OR coldplug, is is true ?
> And if the one I choose change in the furture, my "sed" won't work anymore ?
> :-(
Actually, alsasound should be auto-started after coldplug with
livecd-tools 1.0.22 and I'll be rolling out a catalyst 1.1.10.3 soon
that does *not* add alsasound to any runlevel.
With catalyst 1.1.10.2, you should add alsasound to rcdel, since
catalyst automatically adds it if it sees it, then let autoconfig start
it after coldplug.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-12 18:05 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 23:39 [gentoo-catalyst] livecd-stage1 pkgconfig Christophe PEREZ
2005-07-06 13:47 ` Chris Gianelloni
2005-07-06 18:47 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-08 5:57 ` Christophe PEREZ
2005-07-08 6:20 ` Christophe PEREZ
2005-07-08 14:22 ` Chris Gianelloni
2005-07-08 14:19 ` Chris Gianelloni
2005-07-08 18:21 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-08 19:18 ` Chris Gianelloni
2005-07-08 20:14 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 3:46 ` Christophe PEREZ
2005-07-12 14:12 ` Chris Gianelloni
2005-07-12 16:32 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 17:01 ` Chris Gianelloni
2005-07-12 17:26 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 17:34 ` Christophe PEREZ
2005-07-12 18:06 ` Chris Gianelloni
2005-07-12 19:17 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 18:05 ` Chris Gianelloni [this message]
2005-07-12 19:14 ` [gentoo-catalyst] Re: Re: " Christophe PEREZ
2005-07-12 19:43 ` Christophe PEREZ
2005-07-12 19:59 ` Chris Gianelloni
2005-07-12 20:18 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 5:03 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 13:14 ` Chris Gianelloni
2005-07-14 17:29 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 18:06 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 18:21 ` Chris Gianelloni
2005-07-14 18:33 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 18:42 ` Christophe PEREZ
2005-07-14 18:57 ` Chris Gianelloni
2005-07-14 19:36 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-14 19:53 ` Chris Gianelloni
2005-07-15 0:52 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-15 15:31 ` Chris Gianelloni
2005-07-15 18:37 ` [gentoo-catalyst] " Christophe PEREZ
2006-09-16 19:49 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-09 5:52 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-09 7:00 ` Christophe PEREZ
2005-07-09 13:56 ` Paul Smith
2005-07-09 17:18 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 3:42 ` Christophe PEREZ
2006-04-16 3:10 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-17 13:02 ` Chris Gianelloni
2006-04-17 15:47 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-10 4:26 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-11 19:25 ` Christophe PEREZ
2005-07-11 19:44 ` Chris Gianelloni
2005-07-11 21:04 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-12 22:23 ` Christophe PEREZ
2005-07-13 4:04 ` Christophe PEREZ
2005-07-13 14:26 ` Chris Gianelloni
2005-07-13 15:23 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-13 15:38 ` Michiel de Bruijne
2005-07-13 15:38 ` Chris Gianelloni
2005-07-13 16:57 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-13 17:05 ` Chris Gianelloni
2005-07-13 17:34 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-13 18:22 ` Chris Gianelloni
2005-07-13 19:35 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-13 19:47 ` [gentoo-catalyst] " Chris Gianelloni
2005-07-13 19:53 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-13 17:38 ` [gentoo-catalyst] Re: " Christophe PEREZ
2005-07-11 21:04 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-11 21:17 ` Chris Gianelloni
2005-07-11 21:33 ` [gentoo-catalyst] " Christophe PEREZ
2005-07-11 21:19 ` [gentoo-catalyst] " Christophe PEREZ
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=1121191505.11002.46.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-catalyst@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