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