Recent Posts

1

Programming & Scripting - Unofficial / Re: firefox_update.sh - Efficiently Update firefox.tcz

« Last post by gadget42 on Today at 03:20:44 AM »

mostly for future thread visitors, some links with potentially historical value:
https://bugzilla.mozilla.org/show_bug.cgi?id=1964277
https://support.mozilla.org/en-US/questions/1154387
https://support.mozilla.org/en-US/kb/update-failed-error-message-when-updating
https://support.mozilla.org/en-US/kb/update-firefox-latest-release
https://www.mozilla.org/en-US/firefox/all/
https://www.mozilla.org/en-US/firefox/all/desktop-release/

also of note with regards to installing/updating for windows users(bolding/italics/underlining mine):

Learn about installers > Microsoft Store

This option will open a Firefox product page in the Microsoft Store web portal. If you are running Windows 10 or Windows 11, you will have the option to open the Microsoft Store from this page and install Firefox. If you install from the Microsoft Store, updates to Firefox will also be handled by the Microsoft Store. There are minor differences in Firefox behaviors and capabilities when installed from the Microsoft Store, but for most users these differences are not noticeable.

IMHHO, doing manual installs and/or updates circumvents certain counting/polling/etc and as such is to be "officially" discouraged...ha!

@CNK, please keep us posted on any new knowledge!
(also agree on the dillo sentiments)

2

Programming & Scripting - Unofficial / Re: firefox_update.sh - Efficiently Update firefox.tcz

« Last post by CNK on May 17, 2025, 11:37:57 PM »

Well that didn't last long, Firefox just changed how their updater program works and they won't say how to use it now. If I figure it out I'll post a new version.

Oh how I wish I could just do everything in Dillo...

3

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by CNK on May 17, 2025, 11:31:00 PM »

... FetchExt.sh, running on any machine, could now use "file" to work out the TC kernel version of the system that will use the downloaded extensions. ...

Let me put it another way. I'm not interested in trying to figure out
all of the different places vmlinuz might be stashed, or how some
users might decide to rename vmlinuz. This script is also designed
to support piCore. If I'm not mistaken, it gets packaged with multiple
kernels.

OK, that's fine. Just a suggestion since it's something I'd like in order to minimise downloads and storage. But I'll just modify it to do that myself.

4

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by Rich on May 17, 2025, 11:16:13 PM »

Hi GNUser
Wanna play?
I've attached the updated Fetch.sh.
The current version of ShowErrors.sh is also attached to keep them in the same post.
The posted versions in reply#33 will eventually be deleted.

These are the changes to Fetch.sh:

Code: [Select]

# Version 0.6 May 17, 2025
# Added SanitizeExtName() to support Filename-KERNEL from command line.
# Added CheckArgs() to enforce ARCH and TC restrictions.
# Changed armv* to arm* in BuildVersionsList() so it also detects armhf.
# Simplified RefreshInfoList().
# Updated help message to include $Version, $ARCH, $TC, and note about
#     valid values for ARCH based on TC version.
This is the revised help message:

Code: [Select]

FetchExt.sh Version 0.6 May 17, 2025

Usage:

        FetchExt.sh ExtensionName ExtensionName ExtensionName
                                Fetches the extension(s) and its dependencies.
                                ExtensionName is case sensitive.
                                Including  .tcz  is optional.

        FetchExt.sh info        Fetches the list of available extensions in the
                                listed repository and displays it using less in
                                a new terminal.

        FetchExt.sh Log Displays the Log.txt file (if it exists) using less
                                in a new terminal.

        Please see the User variables section of this script for
        setting the version and architecture you will download for.
        Current settings are  TC=15.x    ARCH=x86

        Note about ARCH:
        Up to TC14,  options are  x86  x86_64  armv6  armv7  armv7l  aarch64
        TC15 and up, options are  x86  x86_64  armhf  aarch64

5

Raspberry Pi / Re: aarch64 chromebook compatibility

« Last post by Paul_123 on May 17, 2025, 10:58:57 PM »

This is a raspberry pi bootLoader/firmware and kernel.  But other binary extensions should run on other arm chips.

6

Raspberry Pi / aarch64 chromebook compatibility

« Last post by Comptr-User on May 17, 2025, 09:45:37 PM »

I was looking into installing a linux distro on my chromebook, and I thought that TinyCore would be a good choice considering my chromebook's low processing power and 4gb of ram. It has a MediaTek MT 8183 CPU, which is an aarch64 cpu.
I understand that it is difficult at best and impossible at worst to get a custom os on an ARM chromebook, but I want to know if this port (or any port/version tbh) of TinyCore even has support for the hardware in the first place.
Sorry if this is a bit of a newbie or frequently asked question.

7

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by Rich on May 17, 2025, 09:42:18 PM »

Hi CNK

... FetchExt.sh, running on any machine, could now use "file" to work out the TC kernel version of the system that will use the downloaded extensions. ...

Let me put it another way. I'm not interested in trying to figure out
all of the different places vmlinuz might be stashed, or how some
users might decide to rename vmlinuz. This script is also designed
to support piCore. If I'm not mistaken, it gets packaged with multiple
kernels.

The current method is, in my opinion, fairly bulletproof.
There is no guesswork on version numbers, you get them all. tce-load
will load the correct one and ignore the rest. That guarantees it won't
fail due to incorrect module versions.

I'm putting the final touches on the new version now. I will post again
when it is ready for testing.

8

TCB Q&A Forum / Re: LZMA2 in tar

« Last post by yvs on May 17, 2025, 02:44:26 PM »

If it works with smaller archives, likely that dictionary size is too big for embedded version.

9

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by CNK on May 17, 2025, 11:13:47 AM »

But the script could still try looking in likely places such as "../../vmlinuz" or "../../boot/vmlinuz" for it, which might work for common TC installations.

I think the main reason  FetchExt.sh  is so useful is that it can run on any machine, whether or not TCL is present anywhere on that machine.

Yes that's the situation I'm talking about!

Somehow nobody's understanding me, so I'll try a more complete example:

Code: [Select]

$ mount /mnt/sdb1
$ cd /mnt/sdb1/tce/optional
$ file ../../vmlinuz64
../../vmlinuz64: Linux kernel x86 boot executable bzImage, version 6.6.8-tinycore64 (tc@box) #666 , RO-rootFS, swap_dev=0x5, Normal VGA
$ ~/bin/FetchExt.sh input-joystick-KERNEL

FetchExt.sh, running on any machine, could now use "file" to work out the TC kernel version of the system that will use the downloaded extensions.

"file" != "uname": its output is unrelated to the system it's running on, "file" can tell you the version of any kernel binary file (vmlinuz). You just need to find the location of that file for the TC installation that's going to use the extensions that FetchExt.sh is downloading - likely close to the tce/optional directory (though not always).

10

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by GNUser on May 17, 2025, 06:42:10 AM »

But the script could still try looking in likely places such as "../../vmlinuz" or "../../boot/vmlinuz" for it, which might work for common TC installations.

I think the main reason  FetchExt.sh  is so useful is that it can run on any machine, whether or not TCL is present anywhere on that machine.