Tiny Core Linux

Tiny Core Base => TCB News => Final Releases => Topic started by: Juanito on March 31, 2025, 05:38:35 AM

Title: Tiny Core v16.0
Post by: Juanito on March 31, 2025, 05:38:35 AM
Team Tiny Core is proud to announce the release of Core v16.0
http://www.tinycorelinux.net/16.x/x86/release
http://www.tinycorelinux.net/16.x/x86_64/release

Changelog for 16.0:
* kernel updated to 6.12.11
* glibc updated to 2.40
* gcc updated to 14.2.0
* binutils updated to 2.43.1
* e2fsprogs base libs/apps updated to 1.47.1
* util-linux base libs/apps updated to 2.40.2
* zlib base lib updated to 1.3.1

* getTime.sh: support more than one server from dhcp from miesi-ionos
* update-everything: offer to remove deprecated extensions from bdantas
* tc-function remove mount/umount from bb list from CardealRusso
* provides.sh: Rich's improved versions: update from CardealRusso
* linuxrc: remove symlink from GNUser
* update-everything: backup stale .dep files form bdantas
* tce-load: add missing sudo to rmdir command in copyInstall() from Rich
* tce-load, tce-setup: changes from idk
* tce-setup: fix syntax error from bdantas

Not in the base, but also updated:
* mirrorpicker: grab info.lst from 15.x
* mirrorpicker: explicitly use bb wget
* editor: various changes from Rich

Note also that the fltk_projects in x86_64 have been updated to use fltk-1.4 with x11 and wayland. In the interests of minimising bloat the x86 fltk_projects remain with fltk-1.3 x11 only.
Title: Re: Tiny Core v16.0
Post by: Uncle Warthog on March 31, 2025, 05:12:47 PM
I'm having some issues with the Apps GUI application in both the 32 and 64 bit versions.  The problem in both is that I am unable to load apps locally from the GUI menu.  All of my downloaded apps appear but selecting one for installation does nothing and gives no error message.  Installing one manually using the tce-load -i command line loader pointing it to the physical location of the application seems to work fine.  Also, using the browse menu to find the application online then selecting it for download and load works fine; in the download window, I can see it scroll through the application and list of dependencies but they are not downloaded as they already exist in the tce location then the application is loaded and can be run.

Also, onboot maintenance, at least in the 64-bit version (I have not checked the 32-bit version yet) does not appear to work correctly, with a problem possibly related to the local loading.  I'm presented with a list of apps as usual but the onboot list in the right half of the window is blank.  I can select an application to be added to the onboot list but no change is made to the onboot list, either in the window or on disk.  Editing the onboot list file manually with vi or another text editor seems to work fine.

This appears to be a new problem in TCL 16.0, TCL 15.0 worked fine for both of these things.

Any help you can give me with this would be greatly appreciated.
Title: Re: Tiny Core v16.0
Post by: CNK on March 31, 2025, 09:19:03 PM
Following on from discussion on failure to boot on 486 and VIA C7 CPUs in the TC16 Alpha/Beta testing threads:

486

Although I found some 16MB RAM sticks to try and upgrade my 486 desktop PC to 36MB RAM, it looks like the 486 reboot problem is definitely in the kernel code anyway. I finally dug up this patch (https://lore.kernel.org/lkml/CANpbe9Wm3z8fy9HbgS8cuhoj0TREYEEkBipDuhgkWFvqX0UoVQ@mail.gmail.com/) in the kernel mailing list from Oct. 2024. The author says the first bug fixed by it "causes immediate reboot" on CPUs without CPUID support (486s).

Looking though the Git log for the patched file in the kernel sources (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/arch/x86/kernel/head32.c) it doesn't seem to have been merged, though it's not clear why. I guess then that all current unpatched kernels since v6.7-rc1 fail on 486 CPUs (the TC15 kernel was v6.6.8).

I'd ask about adding that patch to the TC16 kernel, but since it's released now I guess I'm a few hours too late...

VIA C7

I did similar searching for the VIA C7 issue and found lots of hits for random freezes like with the printk kernel, but in that case they were all pretty ancient bugs, nothing recent. However I haven't found a suggestion of a fix ever being made, newer software versions apparantly just started working again. My guess is that the bug is still rolling around in the kernel code somewhere, intermittently getting triggered by different glibc builds, or this time by the non-printk kernel build itself, when the compiler happens to optimise it in a certain way that triggers the hang condition. Or I guess it could just be a coincidence.

2008 - Gentoo bug 228263 - sys-libs/glibc-2.6.1 plus VIA C7 CPU plus load freeze box (https://bugs.gentoo.org/show_bug.cgi?id=228263)
2008 - Debian Bug 507845 - Dedibox server with VIA C7 cpu freeze with the last libc6 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507845)
2008 - Kernel mailing list discussion - strange freeze with VIA C7 dedicated server and libc 2.6.1 (https://lore.kernel.org/lkml/2ffbcf00806232001o4bd314f4kc590e43b4ab27076@mail.gmail.com/)
2007 - Kernel mailing list discussion - similar sounding issue fixed with some X86_CMPXCHG64 patch (https://lore.kernel.org/lkml/Pine.LNX.4.64.0705191820100.11197@merry.kedzierski.org/) - possibly related CONFIG_X86_CMPXCHG64 (https://boxmatrix.info/wiki/Property:CONFIG_X86_CMPXCHG64) kconfig option removed in v5.15.153.
2007 - unanswered Kernel mailing list post - VIA spurious hang on 2.6.23.1 (https://lore.kernel.org/lkml/Pine.LNX.4.64.0711201606330.32378@fbirervta.pbzchgretzou.qr/)

On my VIA C7-M system I tried "clocksource=jiffies" and related kernel commands, and failed to enable any more debugging info with "sched_debug", nothing had any affect with the standard kernel. There are more suggestions in the threads above, but they never seemed to help anyone back then...
Title: Re: Tiny Core v16.0
Post by: Rich on April 01, 2025, 12:34:26 AM
Hi Uncle Warthog
... The problem in both is that I am unable to load apps locally from the GUI menu. ...
Confirmed. I'll try to take a look tomorrow to see if I can spot the problem.
Title: Re: Tiny Core v16.0
Post by: Juanito on April 01, 2025, 01:57:45 AM
Although I found some 16MB RAM sticks to try and upgrade my 486 desktop PC to 36MB RAM, it looks like the 486 reboot problem is definitely in the kernel code anyway. I finally dug up this patch (https://lore.kernel.org/lkml/CANpbe9Wm3z8fy9HbgS8cuhoj0TREYEEkBipDuhgkWFvqX0UoVQ@mail.gmail.com/) in the kernel mailing list from Oct. 2024. The author says the first bug fixed by it "causes immediate reboot" on CPUs without CPUID support (486s).

Looking though the Git log for the patched file in the kernel sources (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/arch/x86/kernel/head32.c) it doesn't seem to have been merged, though it's not clear why. I guess then that all current unpatched kernels since v6.7-rc1 fail on 486 CPUs (the TC15 kernel was v6.6.8).

I'd ask about adding that patch to the TC16 kernel, but since it's released now I guess I'm a few hours too late...

Before we think about recompiling the kernel, you might want to ask the kernel people why the patch wasn't included?
Title: Re: Tiny Core v16.0
Post by: Rantanplan on April 01, 2025, 10:14:13 AM
Bonjour @Juanito,

Merci à l'équipe de développeurs de Tiny Core Linux et aux testeurs pour cette dernière version de TCL.

Félicitations et Bravo à toute l'équipe.

Amitiés.
Title: Re: Tiny Core v16.0
Post by: Rich on April 01, 2025, 02:14:15 PM
Hi Juanito
I tracked down the issue and pushed the fix to git.

If you see this type of warning when compiling apps, ignore it:
Code: [Select]
warning: ignoring return value of 'bool std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::empty() const [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]', declared with attribute 'nodiscard' [-Wunused-result]   66 | report_type.empty();/code]
Title: Re: Tiny Core v16.0
Post by: Uncle Warthog on April 01, 2025, 04:45:09 PM
Hi Uncle Warthog
... The problem in both is that I am unable to load apps locally from the GUI menu. ...
Confirmed. I'll try to take a look tomorrow to see if I can spot the problem.
Thanks!  Let me know if there's anything you want me to test on my systems.
Title: Re: Tiny Core v16.0
Post by: Rich on April 01, 2025, 04:52:57 PM
Hi Uncle Warthog
Once Xprogs.tcz gets updated with the fix you should see an announcement here.
Title: Re: Tiny Core v16.0
Post by: Juanito on April 02, 2025, 04:56:32 AM
Xprogs updated
Title: Re: Tiny Core v16.0
Post by: Juanito on April 02, 2025, 05:57:28 AM
Release of Core v16.0 reposted with some small changes added that were missed first time.

Release announcement modified to suit.
Title: Re: Tiny Core v16.0
Post by: Uncle Warthog on April 02, 2025, 12:52:34 PM
Thanks!

I've tested and everything seems to be working now except for onboot maintenance in the 64-bit apps GUI (the 32-bit works fine). 
Title: Re: Tiny Core v16.0
Post by: Juanito on April 02, 2025, 12:55:09 PM
If you start apps from a terminal window do you see any error messages?
Title: Re: Tiny Core v16.0
Post by: Uncle Warthog on April 02, 2025, 01:19:52 PM
If you start apps from a terminal window do you see any error messages?

No error messages in the terminal window when I start it and no error messages when trying to use onboot maintenance.

When I try to use onboot maintenance, I get the list of apps in the left side of the window as normal but the right side of the window is completely empty instead of showing the contents of the onboot.lst file.  The system allows me to try to add an entry into the file without errors but the listing in the right side of the window remains blank and the existing onboot.lst file remains unchanged.  I've checked that the file is not marked as read-only and I'm able to edit it using vi or other editors without problems.

I know that onboot functionality itself is working correctly as I can insert and remove entries in the onboot.lst file using vi without problems.  It's just editing it in the apps GUI that isn't working.
Title: Re: Tiny Core v16.0
Post by: Rich on April 02, 2025, 03:06:51 PM
Hi Juanito
I updated my Xprogs and corepure64 files.
When starting apps from the command line, I get an
error when trying to add an extension to onboot.lst:
(https://forum.tinycorelinux.net/index.php?action=dlattach;topic=27578.0;attach=7034)

You can see in the error message it somehow jumbled
the path to onboot.lst and part of /proc/cmdline together.

If you look just above the 2 display windows in apps you
can see more of the text from /proc/cmdline scribbled
across the length.
Title: Re: Tiny Core v16.0
Post by: Uncle Warthog on April 02, 2025, 03:52:28 PM
Juanito & Rich,

I'm seeing the /proc/cmdline there as well; if I'd thought about it a little more, I'd have realized that's what it was.  I still don't see any errors in the terminal used to lauch apps though.
Title: Re: Tiny Core v16.0
Post by: Juanito on April 03, 2025, 04:26:13 AM
So far I've been unable to find the problem, which occurs with x86_64 (and aarch64), but not with x86 (which has not moved to fltk-1.4).

tce-load and tce-setup are identical in x86 and x86_64 (aarch64 is still using the previous versions)
Reverting to the previous versions of tce-load and tce-setup does not help.
Reverting to the previous version of apps does not help

If I revert to the fltk-1.3 version of apps with x86_64 (and aarch64) then onboot maintenance works as expected.

Is this somehow a problem created by compiling apps against fltk-1.4?

Edit: building apps against fltk-1.3 and fltk-1.4 with x86 (and armhf), both work.

Something to do with apps and 64-bit?
Title: Re: Tiny Core v16.0
Post by: CNK on April 03, 2025, 06:42:03 PM
Before we think about recompiling the kernel, you might want to ask the kernel people why the patch wasn't included?

OK, I'll ask there on the weekend. I figured I'd better test the patch myself before doing that, so I compiled the TC16 kernel with the patch applied (http://www.ombertech.com/cnk/tinycore/tc16_x86_vmlinuz_cpuid_check), and sure enough it no longer reboots at start-up on my 486s. It does need >16MB of RAM now too though, since on the laptop the boot fails later when it runs out of memory (with error messages though).

Also that kernel boots on my VIA C7-M system. Maybe because I used GCC v12 to build it instead of the newer GCC Juanito used (GCC v14). I haven't tested for hangs during use (that might need rebuilding glibc with an older GCC version too?). I'm not suggesting TC16 revert to older GCC, just posting my observations.
Title: Re: Tiny Core v16.0
Post by: Rich on April 04, 2025, 12:58:43 PM
Hi Juanito
... Something to do with apps and 64-bit?
No, something to do with apps and a "comparing ints of different signedness"
warning that I fixed incorrectly.

I changed this:
Code: [Select]
if ( sloc == string::npos ) {
to this:
Code: [Select]
if ( (unsigned)sloc == string::npos ) {
When it should have been this:
Code: [Select]
if ( (long unsigned)sloc == string::npos ) {
I'll push the fix to git.
Title: Re: Tiny Core v16.0
Post by: Rich on April 04, 2025, 02:31:29 PM
Hi Juanito
I pushed the fix to git.
Title: Re: Tiny Core v16.0
Post by: Juanito on April 05, 2025, 03:49:36 AM
tc-16.x reposted and release notes adjusted
Title: Re: Tiny Core v16.0
Post by: nikovuksan on April 10, 2025, 08:10:42 PM
I want to thank you for your work and such a wonderful system. I use the 64-bit version on a very old Packard Bell Mx52-B016 laptop with an AMD Athlon64 TK-55 dual-core processor at 1.8 GHz, 2 GB of RAM, and a traditional 160 GB hard drive. I usually use Slackware, but on this device, TinyCore runs much more smoothly. I only fall short of using the latest version of Firefox, as I use the latest version of Brave by editing brave-browser.tcz with squashfs-tools with the latest version of Brave for amd64. I also use the latest version of yt-dlp to play YouTube or Twitch videos on mpv with xclip (so I can play up to 720p60). My favorite window manager on this system is icewm, and it runs perfectly. Again, thank you so much for such wonderful work. During the days when the Onboot in the Apps application wasn’t working, I took the opportunity to learn how to edit onboot.lst.. There is always a way to fix things in TinyCore. Wonderful system concept. Best regards.
My native language is Spanish; I used a translator. I hope what I wanted to say can be understood.
Title: Re: Tiny Core v16.0
Post by: MikeLockmoore on April 11, 2025, 05:37:14 PM
I'm still running the RC.   :-[  Guess it's time to upgrade!  :D

I've not seen the new version release announced on DistroWatch yet.  Maybe they will eventually notice, but if the Core team would like a quicker shot of publicity, someone in the Core team should reach out to DW and let them know!   8)
Title: Re: Tiny Core v16.0
Post by: thane on April 19, 2025, 05:47:09 PM
After burning the TinyCorePure64-16.0.iso file to DVD, I get a "failed in waitforX" error when trying to boot from the DVD on my elderly AMD box.

The 15.0.iso DVD boots ok.

As suggested by people who had this issue with earlier versions of TC, I tried loading the Xorg.7.7 extension (tce-load -wi Xorg.7.7). This gave a server error indicating that the md5 file could not be found.

Any suggestions appreciated!

Thane
Title: Re: Tiny Core v16.0
Post by: Rich on April 19, 2025, 10:37:33 PM
Hi thane
I checked the repo, Xorg-7.7.tcz.md5.txt is present.
The md5.txt files for all dependencies in Xorg-7.7.tcz.tree are also present.
Is it possible you actually entered  tce-load -wi Xorg.7.7  instead of  tce-load -wi Xorg-7.7 ?
Title: Re: Tiny Core v16.0
Post by: thane on April 20, 2025, 05:04:18 AM
Hi Rich, that was the issue [bangs head]. Thanks.
Title: Re: Tiny Core v16.0
Post by: thane on April 20, 2025, 02:22:06 PM
False alarm anyway. Think there was something flaky about the DVD. When I burned the ISO to another DVD it booted to the desktop fine. After install the USB boot failed with the waitforX error, but I was able to correct that by installing Xorg-7.7 and the appropriate video extension.

Thanks again for the help!

Thane
Title: Re: Tiny Core v16.0
Post by: CNK on April 25, 2025, 07:11:44 PM
Before we think about recompiling the kernel, you might want to ask the kernel people why the patch wasn't included?
OK, I'll ask there on the weekend.

They settled on this patch which fixes booting on 486 (https://lore.kernel.org/lkml/20250414095933.GAZ_zchcLNPpUHF9IN@fat_crate.local/). I can't work out how to track progress towards that being merged with the main kernel source tree. I gather there are later stages of review and I don't know if you'd want to wait for that.

Though the patch works with later kernel versions, I had to manually make the small changes to arch/x86/kernel/cpu/microcode/amd.c in the kernel v6.12.11 sources because something had changed which meant "patch" couldn't find the location for the new changes.

The TC kernel does need more than 16MB RAM now, although I built a smaller kernel (http://www.ombertech.com/cnk/tinycore/tc16_x86_vmlinuz_cpuid_check_smaller) with things like SMP, ACPI, and NFS support disabled and it boots fine on that 486 laptop with 16MB RAM.
Title: Re: Tiny Core v16.0
Post by: Paul_123 on April 25, 2025, 09:13:50 PM
It would get merged in this repo once approved and back ported.  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/?h=linux-6.12.y

Is there much value in rebuilding TC for this, with the whole 16mb issue?  Or are these devices stuck with custom kernels from here?
Title: Re: Tiny Core v16.0
Post by: nikovuksan on April 25, 2025, 09:26:28 PM
I created a script with the help of Copilot to update the version of brave-browser.tcz (you need to have it installed beforehand) to the latest version available on GitHub (release). I hope it’s useful!

Code: [Select]
#!/bin/sh

# Variables
EXECDIR=/tmp/brave-build/usr/local/bin/brave.com/brave
TEMP_DIR=/tmp/brave-build
OUTPUT_DIR=/etc/sysconfig/tcedir/optional
GITHUB_API_URL="https://api.github.com/repos/brave/brave-browser/releases/latest"
FILE_PREFIX="brave-browser-"
FILE_SUFFIX="-linux-amd64.zip"
SHA_SUFFIX="-linux-amd64.zip.sha256"

# Comprobar dependencias
for cmd in curl wget unsquashfs unzip mksquashfs shasum; do
    if ! command -v $cmd > /dev/null; then
        echo "Error: La herramienta '$cmd' no está instalada. Por favor, instálala antes de continuar."
        exit 1
    fi
done

# Borrar directorio preexistente
rm -rf $TEMP_DIR

# Descomprimir tcz original y borrar contenido dentro de $EXECDIR
cp -f /etc/sysconfig/tcedir/optional/brave-browser.tcz /tmp
unsquashfs -d /tmp/brave-build/ /tmp/brave-browser.tcz
rm -rf $EXECDIR/*
rm -f /tmp/brave-browser.tcz
cd $TEMP_DIR

# Obtener la última versión desde la API de GitHub
LATEST_VERSION=$(curl -s $GITHUB_API_URL | grep "tag_name" | sed 's/.*"v\([0-9.]*\)".*/\1/')

# Crear la URL de descarga del archivo y su SHA256
BRAVE_URL="https://github.com/brave/brave-browser/releases/download/v$LATEST_VERSION/${FILE_PREFIX}${LATEST_VERSION}${FILE_SUFFIX}"
SHA_URL="https://github.com/brave/brave-browser/releases/download/v$LATEST_VERSION/${FILE_PREFIX}${LATEST_VERSION}${SHA_SUFFIX}"

# Descargar la última versión de Brave  y el archivo .sha256
wget -O brave-browser.zip $BRAVE_URL
if [ ! -f brave-browser.zip ]; then
    echo "Error: No se pudo descargar el archivo desde $BRAVE_URL"
    exit 1
fi

wget -O brave-browser.zip.sha256 $SHA_URL
if [ ! -f brave-browser.zip.sha256 ]; then
    echo "Error: No se pudo descargar el archivo SHA256 desde $SHA_URL"
    exit 1
fi

# Verificar la suma SHA256
echo "Verificando la suma SHA256..."
CHECKSUM=$(shasum -a 256 brave-browser.zip | awk '{print $1}')
EXPECTED_CHECKSUM=$(cat brave-browser.zip.sha256 | awk '{print $1}')

if [ "$CHECKSUM" != "$EXPECTED_CHECKSUM" ]; then
    echo "Error: La suma SHA256 no coincide. Descarga corrupta."
    exit 1
fi
echo "Suma SHA256 verificada correctamente."

# Extraer los archivos del paquete .zip
unzip brave-browser.zip -d $EXECDIR
rm -f brave-browser.zip

# Crear el paquete .tcz
mksquashfs $TEMP_DIR brave-browser.tcz -noappend
if [ ! -f brave-browser.tcz ]; then
    echo "Error: No se generó el archivo brave-browser.tcz"
    exit 1
fi

# Verificar permisos de escritura en el directorio de salida
if [ ! -w $OUTPUT_DIR ]; then
    echo "Error: No tienes permisos para escribir en $OUTPUT_DIR"
    exit 1
fi

# Comprobar si el archivo .tcz existe
if [ ! -f brave-browser.tcz ]; then
    echo "Error: No se generó el archivo brave-browser.tcz"
    exit 1
fi

# Mover el paquete al directorio de TinyCore
mv -f brave-browser.tcz $OUTPUT_DIR

# Limpiar el directorio temporal
rm -rf $TEMP_DIR

echo "El paquete brave-browser.tcz  version $LATEST_VERSION ha sido creado y se copio en $OUTPUT_DIR"

    [Edit]: Added code tags.  Rich
Title: Re: Tiny Core v16.0
Post by: Rich on April 25, 2025, 09:47:26 PM
Hi nikovuksan

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

Quote
[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:
Code: [Select]
[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.
Title: Re: Tiny Core v16.0
Post by: nikovuksan on April 25, 2025, 10:03:38 PM
Hi Rich, I'll keep that in mind next time, thanks.
Title: Re: Tiny Core v16.0
Post by: CNK on April 25, 2025, 11:40:20 PM
It would get merged in this repo once approved and back ported.  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/?h=linux-6.12.y

OK, though I hadn't assumed it would be back-ported. I gather it will go into a relevent maintainer's tree first and get reviewed there before being merged but either it hasn't happend yet or I'm looking in the wrong place.

Is there much value in rebuilding TC for this, with the whole 16mb issue?  Or are these devices stuck with custom kernels from here?

The 16MB issue was just on my laptop, and someone here proposed that limited RAM might be my issue rather than a kernel bug. It turns out both were issues, so I just mentioned it to clarify that. On another PC with 20MB RAM the full TC-configured kernel boots OK once patched. Other 486 motherboards (https://redhill.net.au/b/b-95.php) can take 64MB, or even 128MB (https://theretroweb.com/motherboards/s/fic-486-pio2).
Title: Re: Tiny Core v16.0
Post by: Juanito on April 26, 2025, 06:09:37 AM
I see that the kernel developers are speaking of dropping support for i486 and early i586.
Title: Re: Tiny Core v16.0
Post by: CNK on April 26, 2025, 07:50:15 AM
I see that the kernel developers are speaking of dropping support for i486 and early i586.

Ah, yes reported here (https://www.phoronix.com/news/Linux-RFC-Remove-i486-Early-586). Well that's disappointing.
Title: Re: Tiny Core v16.0
Post by: rhermsen on May 24, 2025, 07:50:50 PM
On TCL-16.0 (32-bit) I get the following error when searching for an extension providing an executable:

Quote
$ tce-ab
tce-ab - Tiny Core Extension: Application Browser

S)earch P)rovides K)eywords or Q)uit:
Enter search term, e.g. iwconfig: diff
awk: cmd. line:1: fatal: cannot open file `/etc/sysconfig/tcedir/provides.db' for reading: No such file or directory
S)earch P)rovides K)eywords or Q)uit:

Can someone verify if you have the same behavior?
(still need to try on 64-bit)

Quote
$ uname -a
Linux testapps 6.12.11-tinycore #1 SMP Sun Jan 26 18:37:07 UTC 2025 i686 GNU/Linux

Quote
$ version
16.0



Edit
For CorePure64 I see a bit similar issue:
Quote
S)earch P)rovides K)eywords or Q)uit:
Enter search term, e.g. iwconfig: diff
awk: /etc/sysconfig/tcedir/provides.db: No such file or directory
S)earch P)rovides K)eywords or Q)uit:

Quote
$ uname -a
Linux testapps 6.12.11-tinycore64 #1 SMP Sun Jan 26 16:50:13 UTC 2025 x86_64 GNU/Linux

Quote
$ version
16.0
Title: Re: Tiny Core v16.0
Post by: Rich on May 24, 2025, 09:53:54 PM
Hi rhermsen
Both x86 and x86_64 versions of TC16 tce-ab work.

I was able to recreate your results. I think your error is
due to tce-ab not being able to download provides.db.

Maybe your network is not up?
Maybe your /opt/tcemirror file is messed up?

I unplugged my network cable and got the same result as you.
Title: Re: Tiny Core v16.0
Post by: rhermsen on May 25, 2025, 05:20:18 PM
I have not seen any other issues except with the 'P' option with tce-ab.

With CL-15.0 it is working.
(below is all from CL-15.0)
Scrolling up from the clear screen I do see some messages, but only the first time I try tce-ab:
Code: [Select]
$ tce-ab
tce-ab - Tiny Core Extension: Application Browser

S)earch P)rovides K)eywords or Q)uit:
Enter search term, e.g. iwconfig: diff
open: No such file or directory
not using seed file /etc/sysconfig/tcedir/provides.db
tce - Tiny Core Extension browser
         1. atom-apm.tcz
         2. atom.tcz
         3. bash-completion.tcz
         4. bind-dev.tcz

Code: [Select]
$ ls -la /etc/sysconfig/tcedir/provides.db
-rw-rw----    1 tc       staff     29189148 May 25 10:18 /etc/sysconfig/tcedir/provides.db

Trying a second time is without additional messages:
Code: [Select]
$ tce-ab
tce-ab - Tiny Core Extension: Application Browser

S)earch P)rovides K)eywords or Q)uit:
Enter search term, e.g. iwconfig: diff
tce - Tiny Core Extension browser
         1. atom-apm.tcz
         2. atom.tcz
         3. bash-completion.tcz

Code: [Select]
$ uname -a
Linux testapps 6.6.8-tinycore64 #666 SMP Sat Dec 23 16:41:21 UTC 2023 x86_64 GNU/Linux

Code: [Select]
$ version
15.0

Edit
Same behavior with CP64-15.0.
Title: Re: Tiny Core v16.0
Post by: Rich on May 25, 2025, 10:07:20 PM
Hi rhermsen
... Scrolling up from the clear screen I do see some messages, but only the first time I try tce-ab: ...
That's normal if provides.db is not present. tce-ab calls provides.sh
which then runs zsync to see if provides.db is current.

When I run the command the first time, it prints that message
and downloads provides.db because it's not present. The second
time I run it it's quiet:
Code: [Select]
tc@E310:~$ zsync -i provides.db -q http://repo.tinycorelinux.net/10.x/x86/tcz/provides.db.zsync
open: No such file or directory
not using seed file provides.db
tc@E310:~$ zsync -i provides.db -q http://repo.tinycorelinux.net/10.x/x86/tcz/provides.db.zsync
tc@E310:~$
Title: Re: Tiny Core v16.0
Post by: rhermsen on May 26, 2025, 05:21:38 PM
@Rich

I found the reason for download of 'provides.db' to fail.

On my Windows host I have Zscaler running. This is causing the following step in '/usr/bin/provides.sh' to fail:
Code: [Select]
/bin/ping -A -W 1 -c 2 8.8.8.8 2>&1 > /dev/null || return
Running this in terminal with Zscaler enabled:
Code: [Select]
$ /bin/ping -A -W 1 -c 2 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
Disabling 'Internet Security' in Zscaler:
Code: [Select]
$ /bin/ping -A -W 1 -c 2 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=128 time=15.380 ms
64 bytes from 8.8.8.8: seq=1 ttl=128 time=15.613 ms

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 15.380/15.496/15.613 ms

Annoying because Internet Security of Zscaler is enabled automatically.
But now I know how to get it working...
Title: Re: Tiny Core v16.0
Post by: Rich on May 26, 2025, 08:37:45 PM
Hi rhermsen
The ping was added as a quick way to check if the network was up.
If the network is down, attempting a download means waiting for
the download attempt to time out.