Deploying Concerto

Customizing Concerto Player

Help :: Deploying Concerto

Last modified: 9:32 pm on August 2, 2009           Article: 1-35

Concerto Player can be customized through the use of plugins. These plugins contain files which are overlaid on the root filesystem when the system boots. We recommend testing your customizations on a live system first. Once you've determined the files to modify, you can start constructing a plugin. You'll need access to a Linux PC, and you'll need to obtain a copy of the "mksquashfs" tool. Create a directory to hold the files you want to add. For instance, if you wanted to add a file "/etc/test.txt", you'd create a directory "your_plugin", then "your_plugin/etc", and put "text.txt" within "your_plugin/etc". Once the files are ready to go, use the following command to create the plugin: "mksquashfs your_plugin/ your_plugin.plugin -all-root -noappend".

When creating plugins, it's also possible to write scripts which hook into a couple of locations in the boot process. If a plugin places an executable script in "/etc/init_tasks", the script will be run at the time the system boots. Scripts placed in "/etc/tasks" are run continuously while the system is operating. The script "/sbin/concerto_init" is responsible for this process - it automatically respawns scripts in "/etc/tasks" if they end or are killed. If it's desirable to manually override this behavior, simply remove the execute bit from the offending script using "chmod", then kill any existing processes.

Got a comment about this page?