A script to aid in troubleshooting Tinycore installations.

[Sashank999]

@Rich
I think it can get the TCL Version from uname command and also the architecture.
Then, it could be used for all TCL Versions (If done Repo URL Formatting for all architectures).

We can add a "Found some custom TCEs :" and list all md5 not found tczs under it.

If user has a custom tce folder, we can find whether he has one by using "showbootcodes | grep tce" command and use that folder as tce directory. Else we can use the stock tcedir.

Can we include color in it ? (just like submitqc)

[Rich]

Hi Sashank999

I think it can get the TCL Version from uname command and also the architecture. ...

You can get the kernel version from  uname , not the TC version. The  version  command returns the TC version.

... Then, it could be used for all TCL Versions (If done Repo URL Formatting for all architectures). ...

It should already work for all TC versions. The repo URL is retrieved using the  getMirror  command provided by  tc-functions.

... If user has a custom tce folder, we can find whether he has one by using "showbootcodes | grep tce" command and use that folder as tce directory. Else we can use the stock tcedir. ...

Already done. See reply #5:
http://forum.tinycorelinux.net/index.php/topic,23936.msg150854.html#msg150854

... Can we include color in it ? (just like submitqc)

submitqc sends its results to the screen. TCscan.sh sends its results to a text file.

[Sashank999]

Oh.
But we can also make it display on the screen with color so that the user can simply find the problem himself and can try possible solutions.
Finding in a text file is difficult (I think so  ).

[Rich]

Hi Sashank999
The script does not identify problems. It gathers basic information about a Tinycore installation. It does not attempt to interpret the
results.

... But we can also make it display on the screen with color so that the user can simply find the problem himself and can try possible solutions. ...

The information saved is intentionally unbiased so the end user determines whether something is really a problem or not.