rqst wiki: ll /usr/bin | grep tce

[ttz]

wiki or addition to 'the book.'

Code: [Select]

>ll /usr/bin/ | grep tce
-rwxr-xr-x 1 root root    2316 Sep 10  2014 tce
-rwxrwxr-x 1 root staff   2232 Sep 10  2014 tce-ab
-rwxrwxr-x 1 root staff   5744 Sep 10  2014 tce-audit
-rwxr-xr-x 1 root root     323 Sep 10  2014 tce-fetch.sh
-rwxr-xr-x 1 tc   staff   8020 Sep 10  2014 tce-load
-rwxrwxr-x 1 root staff   1162 Sep 10  2014 tce-remove
-rwxrwxr-x 1 tc   staff    620 Sep 10  2014 tce-run
-rwxrwxr-x 1 root staff   2312 Sep 10  2014 tce-setdrive
-rwxr-xr-x 1 root root    4644 Sep 10  2014 tce-setup
-rwxrwxr-x 1 root staff   2104 Sep 10  2014 tce-size
-rwxrwxr-x 1 root staff   1107 Sep 10  2014 tce-status
-rwxrwxr-x 1 root staff   7511 Sep 10  2014 tce-update
-rwxrwxr-x 1 root staff    464 Sep 10  2014 tcemirror.sh


>version
5.4
i think understanding these would make me a better usr/member. tce and tce-ab seem related. in core (not tinycore) 6.3 tce-ab is a ln to tce. the resulst of:

Code: [Select]

diff tce tce-ab
in tinycore 5.4 and 6.1 are different.

i'm trying to understand the tce* scripts. i'm not a coder/programmer so reading the code is so very difficult especially without comments.

i'll keep trying, but a clear, explanatory wiki would help so very much.

thank you,
ttz

[coreplayer2]

hi, think of it this way..

tce = Tiny Core Extension

Code: [Select]

tce-ab - Tiny Core Extension: Application Browser

S)earch P)rovides K)eywords or Q)uit:
tce-ab "Tiny Core Extension: Application Browser" is the command-line application browser and installer for core users (without a desktop interface), whereas APPS is the Application Browser for tinycore users with a desktop

[Greg Erskine]

Hi ttz,

I believe on newer versions tce-ab is linked to tce (it was also called ab at one time) and not all the tce related scripts have "tce" in the name. 

See my very short thread: Why tce and tce-ab scripts?

regards
Greg

[ttz]

i appreciate the replies i've rcv'd, but they seem to focus too much on tce[-ab]. that was not my intent. trying to more clearly express intent:

for any tce* script, what is the goal; what is the usage? i know i can, for example:

Code: [Select]

tce-load --help
that does not teach. a wiki does/can. tc wiki and 'book' are full of info but not what i'm looking for at the moment.

if my request is understood, the value should be too. is the request too close to request for hand-holding? if so, just say so; it is ok!

[ttz]

@Greg Erskine

i've checked "Why tce and tce-ab scripts?"

but don't know what to get from it. my best is to gather that u'v had a roughly similar Q.

[ttz]

@Greg Erskine

not all the tce related scripts have "tce" in the name.

that is helpful; indirectly, but helpful. i guess u mean things like 'backup.'

[Greg Erskine]

@Greg Erskine

i've checked "Why tce and tce-ab scripts?"

but don't know what to get from it. my best is to gather that u'v had a roughly similar Q.

Hi ttz,

I recently when through the process you have just begun. I didn't what to give you any spoilers in case you wanted to discover for yourself. 

From what I can work out, tce-ab was once tce, and before that ab. In recent versions of tc, there was, by mistake, both tce and tce-ab and they were almost identical. At least in piCore, only one file remains, tce, and a symbolic link from tce-ab to tce. So you can type tce or tce-ab and run the same program. As you start reading through the documentation you will see references to all 3 names.

search.sh, provides.sh from memory are called from the tce* scripts.

Also, some of the command write files to /tmp that are worth looking at. i.e. "tce-audit builddb" creates  /tmp/audit_results.txt and /mnt/mmcblk0p2/tce/optional/tce.db

regards
Greg

[ttz]

@Greg Erskine

i will continue to discover!

thank you,
ttz