Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: aus9 on January 05, 2026, 11:41:51 PM
-
I have a potential TCE that I needed to run make on....because it actually used gawk to generate the script.
So it was not possible to grab a pre-made bash script from the source.
Do you agree that if something is "compiled" on say x86_64 that makes a bash script, the actual script is truly any arch?
I accept there may be differences in some TCE names TC32 vs TC64 vs RPi
that might be needed to provide some functions of that script.
file exe-name returns "Bourne-Again shell script, Unicode text, UTF-8 text executable"
thanks for reading
-
It's no bash it's ash(busybox (https://en.wikipedia.org/wiki/Almquist_shell))
https://github.com/tinycorelinux/Core-scripts
-
I am confused by your reply due to my poor communicating skills....lets try again
the head of a potential TCE submisison reads
#!/usr/bin/env bash
running file against the /usr/local/bin/executable claims its a "Bourne-Again shell script, Unicode text, UTF-8 text executable"
I am not talking about TCB....is that clearer?
-
I would not make that assumption, unless you have checked.
-
excellent Paul_123....thats what I was looking for.
@Rich
Please mark as solved
-
Hi aus9
... running file against the /usr/local/bin/executable claims its a "Bourne-Again shell script, Unicode text, UTF-8 text executable" ...
That part might concern me a bit. If an end users environment isn't set up
to provide UTF-8 support, will your extension still run correctly?
Marked as solved.
-
If an end users environment isn't set up to provide UTF-8 support, will your extension still run correctly?
well I am testing the product which is translate-shell and I mention this in the info file (subject to change)
Optional or NEEDED TCEs depend on how you wish to use this TCE
1) You must be on a terminal that support UTF-8 to display any
font you input or get as a translation.
2) You need a font TCE to display any input or output font
Remember to restart terminal if you load a new font TCE
SNIP
trans -b
SNIP
我在哪里 # you need wqy-zenhei-fonts-ttf to see font
where am i
-
Hi aus9
Sorry, I wasn't clear. I was referring whether the scripts lines could
be read and executed. The file command inferred the the script
itself was written using UTF-8 characters.
-
I am a dumbo....are you suggesting members need locale setup to use the possible TCE?
-
Hi aus9
I believe that's a distinct possibility.
-
thanks
-
Hi Rich
I am posting things about this script test here at your request
I disagree with your assessment as I think both of us have been tricked with what is loading. I now believe that somehow the booting process....is reading elements from more that one boot list
Here is my alleged proof that you are mislead. That is...mylocale is still loading when I told it not to. Image expires in one month
https://i.postimg.cc/B6wNTV6L/gremlin2.png
1) onboot.lst has no mention of mylocale*
2) bootloader string has no mention of UTF setting nor timezone setting
3) but apps onboot maintenance tells a different story
4) ls installed command confirms that mylocale has loaded.....and that means we are tricked by the bash script
ie I have yet to confirm that script fails
FWIW here is my new bootloader.....and I am booting 17b
menuentry "17a" {
linux /boot/vmlinuz17 home=LABEL=tc1 tce=/mnt/sdb1/17/tce waitusb=10 quiet lang=en_AU.UTF-8 tz=Australia/Perth blacklist=snd-hda-intel nozswap
initrd /boot/amd-ucode.img /boot/rootfs17.gz /boot/modules17.gz
}
menuentry "17b" {
linux /boot/vmlinuz17 home=LABEL=tc1 tce=/mnt/sdb1/17/tce waitusb=10 quiet blacklist=snd-hda-intel nozswap
initrd /boot/amd-ucode.img /boot/rootfs17.gz /boot/modules17.gz
}
and I have only just discovered that I can no longer use a boot code for lst=name.lst
-
Ok I was wrong again. In the past....at my own risk.....I would have only one TC but this time I created a dir called 17 and I was editting the 16 onboot.lst.....YIKES
I failed to read my own bootloader that said I am supposed to edit files under
tce=/mnt/sdb1/17/tce
sorry for my bad testing
I will remove the image links
anyhow lets confirm its a true UTF bash script shall we
locale a
locale: unknown name "a"
tc@box:~$ trans -b
J'adore linux
[WARNING] Connection timed out. Retrying IPv4 connection.
I love linux
Me thinks we have tested this truly now