Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: mbertrand on February 26, 2013, 11:02:34 AM

Title: Disabeling xserver
Post by: mbertrand on February 26, 2013, 11:02:34 AM

What would be the best way to temporally setup Tiny to boot to console and not startx?

Title: Re: Disabeling xserver
Post by: gerald_clark on February 26, 2013, 11:04:10 AM

Use the 'text' boot code.

Title: Re: Disabeling xserver
Post by: mbertrand on February 26, 2013, 11:12:31 AM

Thanks

Title: Re: Disabeling xserver
Post by: mbertrand on February 26, 2013, 11:50:00 AM

Ok, now that x is not running I want to run a none x application on startup. I gather that "~/.X.d" is for x only?
So where would be the right place to run my app at boot. I just try to test some thing without x but with out uninstalling x

Title: Re: Disabeling xserver
Post by: curaga on February 26, 2013, 12:22:25 PM

Either bootsync or bootlocal in /opt, depending on whether your apps needs user input or not.

Title: Re: Disabeling xserver
Post by: mbertrand on February 26, 2013, 01:00:06 PM

Yes I just saw this thanks.

Title: Re: Disabeling xserver
Post by: CentralWare on March 12, 2013, 07:48:07 AM

Quote from: mbertrand on February 26, 2013, 01:00:06 PM

Yes I just saw this thanks.

If you want to leave the system "as is" and do this yourself, you can shut down X (assuming you need the memory/resources for your script) or if you have ample resources, simply press <CTRL> + <ALT> + <F1> to jump over to a non-x shell and CTRL+ALT+F2 to return to the desktop.

To shut down X, here's a crude script I put together to do so for Tiny:

#!/bin/sh
sudo killall wbar
sudo killall flwm
sudo killall Xvesa
sleep 1
sudo umount /tmp/tcloop/flwm
sudo umount /tmp/tcloop/wbar
sudo umount /tmp/tcloop/fltk-1.1.10
sudo umount /tmp/tcloop/Xvesa
sudo umount /tmp/tcloop/Xprogs
sudo umount /tmp/tcloop/Xlibs

Odds are I haven't covered all the bases as there's probably a cleaner way to do this, but for the need I have it works well.
Hope it helps!