Tiny Core Base > TCB Bugs

Startup Scripts

(1/3) > >>

danielibarnes:
I noticed that when tc-config searches for startup scripts (find /usr/local/tce.installed/ -perm -755 -type f) it will not load startup scripts included in a .tcz because they are symbolic links instead of files. I had to include a user.tar.gz in my .tcz extension. Is this a bug or by design? Am I using the feature properly?

mikshaw:
Is it important that your scripts need to be symoblic links? A wrapper script can be used to accomplish basically the same thing as a link:


--- Code: ---#!/bin/sh
exec /path/to/my/startup_script
--- End code ---

danielibarnes:
When loaded, a .tcz extension is loop mounted on /tmp/tcloop/BASENAME. Symbolic links which point to all of the files in the extension are created on the root filesystem (similar to cp -lr). This is a feature of Tiny Core Linux.

danielibarnes:
I noticed that "tce-load" does not check for startup scripts. Can someone with the knowledge please tell me how this should work? I thought that the startup scripts feature was a sort of "autorun" for extensions. Is this not correct?

mikshaw:
Perhaps it is only used for auto-loaded extensions?  I noticed that adding a script to tclocal directory will run during boot even if that script has nothing to do with tce packages.  As a result I put my  persistent bootlocal script there.  I'm guessing it doesn't apply to tce-load, although I'm too sleepy to check it at the moment.

Navigation

[0] Message Index

[#] Next page