Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: bigpcman on September 19, 2009, 11:38:07 AM
-
Why does the bash.tcz become a link file in tce.installed but other tczs are emty files?
tc@box:/usr/local/tce.installed$ ls -l
-lrwxrwxrwx 1 tc staff 45 Sep 17 12:23 bash -> /tmp/tcloop/bash/usr/local/tce.installed/bash
-rw-r--r-- 1 tc staff 0 Sep 17 12:24 cups
-rw-r--r-- 1 tc staff 0 Sep 17 12:23 firewall-2.6.29.1-tinycore
-rw-r--r-- 1 tc staff 0 Sep 17 12:23 openssl-0.9.8h
-rw-r--r-- 1 tc staff 0 Sep 17 12:24 samba3
-
If an extension has a startup script in the extension, the entry in /usr/local/tce.installed is a symlink to the script in the mounted tcz.
If there is no startup script. the entry in /usr/local/tce.installed is created during install to indicate the extension is installed.
-
If an extension has a startup script in the extension, the entry in /usr/local/tce.installed is a symlink to the script in the mounted tcz.
If there is no startup script. the entry in /usr/local/tce.installed is created during install to indicate the extension is installed.
Could you provide some background on why this is so?
-
The entries in /usr/local/tce.installed serve both as the indicator of the extension being installed as well as the startup script if the file is executable. Killing two birds with one stone rather than having a seperate file serve as the startup script.
If /usr/local/tce.installed/bash is present in the system, the appbrowser or tce-load will state the exetnsion is already installed instead of fetching/installing it. During the installing of an bash (if /usr/local/tce.installed/bash does not already exist), /usr/local/tce.installed/bash will be ran as a script if the file exists in the extension as an executable script.