WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Extension only for configurations  (Read 2062 times)

Offline Op.Davoron

  • Newbie
  • *
  • Posts: 17
Extension only for configurations
« on: March 03, 2010, 05:48:16 AM »
Hello,

The situation:
A PC is booting TC over Network with pxeboot.
The PC has no hard-drive and no network share.
The PC gather all extensions on boot from a http-list.

When TC is started, the main extensions get loaded but not configured.

Example: the X-Server get started but with a wrong resolution or wrong input device configs.

I have to do some configurations but don't want to do them manual after the TC starts, I don't want to do them permanently and I want to get the same configurations every time I start the PC.

I have written a script that do the configurations but at the moment i have to remaster each version of TC to add the Script or write some code in the bootlocal.sh that loads the scrip and executes it.

I think I haven't fully understood the “how to create extension-thing” so, maybe someone have the time to help me.

All I want is a extension with a Script to configure my Clients and these script has to get started short after the main boot process so i.e. I can insert a xorg.conf before the X-server get started and so on.

Thank you in advance for the help!
(hope everything is understandable, ask me if something is unclear)

Offline batnas

  • Full Member
  • ***
  • Posts: 122
Re: Extension only for configurations
« Reply #1 on: March 05, 2010, 08:55:00 AM »
I'm having the same problem.
I have installed MC on a small HHD and in grub i call 'tce=hda1'.
It does load all the extensions, but with default config.
How do we do config files permanently??

Otherwise I should call a script on startup, and have it copy/paste my config files, but that is not the optimal way to do it.

\\Batnas

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Extension only for configurations
« Reply #2 on: March 05, 2010, 09:04:14 AM »
Add any config files you have edited to /opt/.filetool.lst.
Add any custom startup code to /opt/bootlocal.sh.
Do a 'filetool.sh backup'.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: Extension only for configurations
« Reply #3 on: March 05, 2010, 09:53:23 AM »
To make a new extension you need the squashfs-tools-4.0 extension installed.

Create a directory for your new extension. For example:

mkdir -p /home/tc/myext

Copy directories and files to myext. You must include directories. For example, if your file is in /usr/local/myfile use /home/tc/myext/usr/local/myfile.

To make a new extension:

sudo su
cd /home
mksquashfs myext/ new-extension-name.tcz

Paste the new extension to the /tce/optional directory.

If you want it to be loaded when you start the computer, add it to CPanel -> Apps Audit -> On Boot.

If you want it to be available on demand, add it to CPanel -> On Demand.

If you want more than one extension to be loaded at the same time, create a .dep file with the names of other extension(s) to be loaded. (If you run CPanel -> Apps Audit -> Dependencies -> Update Dep Database, the .dep file will be removed, so save a copy to put back after running it.)

If you want it to be run when you start the computer, add it to CPanel -> Apps Audit -> On Boot, and add the start command to /opt/bootlocal.sh.


Once you understand how to make extensions, if you use persistent home and opt, and make extensions for anything else you want to save, you don't need to use backup.
Many people see what is. Some people see what can be, and make a difference.