WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Startup Scripts in v3.0  (Read 1820 times)

Offline stasis_22

  • Newbie
  • *
  • Posts: 7
Startup Scripts in v3.0
« on: August 11, 2010, 08:56:37 PM »
Hi There,
I am new to TCL running v3.0 and I can't get my head around startup scripts.
I would like to always boot into the GUI with the terminal window coming up and I cant work out how to do it.

I have read some stuff about extensions
do I need to create a tar file at /usr/local/tce.installed with my script inside (without the .sh)

Thanks
JDS

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Startup Scripts in v3.0
« Reply #1 on: August 11, 2010, 09:23:22 PM »
try append a line in your .xsession :
Code: [Select]
aterm -display :0 &
HTH
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline stasis_22

  • Newbie
  • *
  • Posts: 7
Re: Startup Scripts in v3.0
« Reply #2 on: August 11, 2010, 10:39:33 PM »
Thanks heaps, that got it.
But so I can learn, what does the FAQ mean when it says :
Code: [Select]
"How to use startup scripts?
The directory /usr/local/tce.installed is where TC keeps track of loaded extensions.
Typically this is a 'flag' a zero byte file. Notice that the extension name does not include its file extension.

Now, if you need a startup script then include it in tar file at this location and its name needs to match the extension name. Do make sure that the script works and is executeable. Do not use .sh or any other file extension.

A very simple example is in order:

Take for example the 915resolution.tce extension.
If we want to make a startup script then it would be placed in
/usr/local/tce.installed/915resolution

The actual startup script could be anything that is executeable.
Using the same example, my /usr/local/tce.installed/915resolution is a simple as this:

#/bin/sh
/usr/local/sbin/915resolution 50 1024 600

Note: Be sure to use full paths as during boot no login has occured yet no PATHs are set.

So the final result of a 915resolution.tce with a startup script would contain

usr/local/sbin/915resolution
usr/local/tce.installed/915resolution"

Is that for startup scripts during boot?

Thanks

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11041
Re: Startup Scripts in v3.0
« Reply #3 on: August 12, 2010, 04:43:02 AM »
That entry is for extension startup scripts. See this one :)

http://tinycorelinux.com/faq.html#appstart

The directory .X.d might not exist by default.
The only barriers that can stop you are the ones you create yourself.