Tiny Core Base > TCB Talk

Boot sequence - what starts xvesa xserver?

(1/1)

bigpcman:
I've been digging in a little deeper into tc trying to understand the boot sequence. 

inittab -> init.d/rcS -> tc-config -> desktop.sh -> wbar.sh & jwm_restart ... etc

and can't quite see how the Xvesa Server starts up.

I see /tmp/xsetup_requested &  /etc/sysconfig/Xserver get set in tc-config but what actually uses these variables?

curaga:
~/.xsession is what starts Xvesa.

xsetup_requested is a marker to show the resolution/mouse wizard when requested with the boot code.
/etc/sysconfig/Xserver is an automatic way to use another X server in Micro Core.

bigpcman:

--- Quote from: curaga on June 11, 2009, 04:02:38 PM ---~/.xsession is what starts Xvesa.

xsetup_requested is a marker to show the resolution/mouse wizard when requested with the boot code.
/etc/sysconfig/Xserver is an automatic way to use another X server in Micro Core.

--- End quote ---
Thanks, that moves me along a bit. But what calls ~/.xsession? Can you take me from tc-config to ~/.xsession?

curaga:
Sure :)

tc-config doesn't call anything, after that the ball is back to init.
Init then launches what it is told to do after-boot; it autologins as root.
Root immediately logs in as user tc, using exec to not leave a root shell behind.
As user tc logs in, his login profile is executed. This checks for the bootcode "text", and if not present, starts X by starting .xsession.

Or, file by file:
init -> tc-config -> init -> /root/.profile -> /home/tc/.profile -> /home/tc/.xsession

bigpcman:
Thank you!  :D That's what I was looking for. Now I get it.

Navigation

[0] Message Index

Go to full version