Recent Posts

51

TCE Q&A Forum / Re: Tor Onion web browser

« Last post by JunkYard on June 23, 2026, 05:35:05 PM »

mostly for future thread visitors arriving here after searching for terms such as tor, onion, web, browser, etc:

https://en.wikipedia.org/wiki/Tor_(network)
https://en.wikipedia.org/wiki/Tor_(network)#Firefox/Tor_browser_attacks
https://en.wikipedia.org/wiki/The_Tor_Project
https://en.wikipedia.org/wiki/Tails_(operating_system)

@JunkYard, please note with respect to the Tails operating system that it is for 64-bit hardware and requires multiple gigabytes of ram for minimum operatibility.

Is that why Juanito version would not install right? and comes up with the error message because his is 64 bit and my machine is 32 bit right?

52

Release Candidate Testing / Re: Core v17.1beta1

« Last post by GNUser on June 23, 2026, 01:55:38 PM »

Thanks, Juanito. getMajorVer and getMirror work as expected now

53

Release Candidate Testing / Re: Core v17.1beta1

« Last post by Juanito on June 23, 2026, 08:55:30 AM »

Version adjusted from 17.1.1 -> 17.1

Version number corrected in posts above

54

Off-Topic - Tiny Core Lounge / Artificial intelligence doesn't hallucinate. :)

« Last post by xor on June 23, 2026, 06:30:05 AM »

Artificial intelligence doesn't hallucinate.

I never thought I'd develop software at this level.

This is just a 100 KB HTML file. (It runs at 115 ESR in Firefox)

The screenshot came out larger than the application itself

Those who work with musical notation will instantly understand the level of parser this application is.

55

TCB Talk / Re: What maxim Kernel version for what hardware

« Last post by nick65go on June 23, 2026, 04:54:45 AM »

“are you considering to use a lower-than-latest Linux version for some devices?”, and if so “with what motivation?”.
So… the very genuine question (mostly people have a reason, and often that valuable to learn from): are you considering running older TC versions? And if so “with what benefit”?

I do NOT consider running OLD version of kernel, because:
1. Luckily all my OLD devices are more than capable to run the LATEST kernel (with minim: 1 GB RAM + 16 GB HDD from 20 years ago!!).
2. I have big concern about bugs (securities + low speed) in OLD kernels. Why should I shut myself in the foot IF I have options to not do it.
3. Cost (TCO= Total Cost of Ownership) in EUROS is (for me) low enough to value it less than my time (left on this planet) So I would buy new hardware (less electricity, less noise, more speed, etc).

I do not intend to be arrogant, but I answer specific to my situation, which could be very different than yours.

56

TCB Talk / Re: What maxim Kernel version for what hardware

« Last post by Stefann on June 23, 2026, 01:11:27 AM »

Hi,
I sure appreciate the investigation on this. It’s often very insightful to “know” the basics.
With that said however….
@nick65go, “are you considering to use a lower-than-latest Linux version for some devices?”, and if so “with what motivation?”.

The reason I ask this is that I actually find it quite superb that tinycore allows to use a very recent Linux with very recent gcc on my very old 1core 32bit cpu that I use for my home automation. When I started I used Damn Small Linux but that went out of support. The first 10 years “not updating Linux” was not a big problem but 2 years ago it became very essential. Biggest problem was lack of https support on dsl.
Anyway… just to illustrate where I’m coming from.

So… the very genuine question (mostly people have a reason, and often that valuable to learn from): are you considering running older TC versions? And if so “with what benefit”?

57

Release Candidate Testing / Re: Core v17.1beta1

« Last post by Juanito on June 22, 2026, 01:53:32 PM »

Hmm - think I’ll make it 7.1 then - it could also cause problems elsewhere..

I’ll fix things tomorrow.

58

Release Candidate Testing / Re: Core v17.1beta1

« Last post by GNUser on June 22, 2026, 01:19:21 PM »

Hi Juanito. Going to third decimal place in the TCL version breaks the  getMajorVer  and  getMirror  functions in /etc/init.d/tc-functions:

Code: [Select]

$ . /etc/init.d/tc-functions
$ getFullVer
17.1.1
$ getMajorVer
17.1
$ getMirror
$ echo $MIRROR
http://repo.tinycorelinux.net/17.1.x/x86_64/tcz # correct mirror should be http://repo.tinycorelinux.net/17.x/x86_64/tczI ran into this issue in the past and proposed a fix. I'll try to find it in the forum.

EDIT: I couldn't find what I proposed before, but something like this would work:

Code: [Select]

getMajorVer() {
getFullVer | grep -Eo '^[0-9]+'
}

59

TCE Q&A Forum / Re: Bringing milkytracker to TCE (1st package attempt)

« Last post by Rich on June 22, 2026, 10:21:05 AM »

Hi coderofsalvation

... So far I've been able to create these files:

Code: [Select]

$ ls -la milkytracker-1.06.*
-rw-r--r-- 1 leon users     700 Jun 22 14:09 milkytracker-1.06.err
-rw-r--r-- 1 leon users 1409024 Jun 22 14:01 milkytracker-1.06.tcz
-rw-r--r-- 1 leon users       9 Jun 22 14:01 milkytracker-1.06.tcz.dep
-rw-r--r-- 1 leon users     481 Jun 22 14:01 milkytracker-1.06.tcz.info
-rw-r--r-- 1 leon users      48 Jun 22 14:01 milkytracker-1.06.tcz.list

 ----- Snip ----- ...

You are missing  milkytracker-1.06.tcz.md5,txt.
I recommend installing  submitqc.tcz  if you plan on submitting extensions.

Then:

Code: [Select]

cd directory/containing/.tcz/files
submitqc --libssubmitqc  will create  .tcz.md5.txt  and  .tcz.list  if not present or incorrect.

... All works **almost** fine, when running:

Code: [Select]

$ tce-load -i milkytracker-1.06.tgz
$ milkytracker
SDL: SDL_CreateWindow (width: 1280, height: 960) failed: Failed loading libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory
Retrying with default size...SDL: SDL_CreateWindow (width: 640, height: 480) failed: Failed loading libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory

 ----- Snip -----
This will error on a basic TC (which has no libGL installed)...which is probably MOST of the users.

 ----- Snip -----

First I was thinking in renaming /usr/bin/milkytracker to /usr/bin/milkytracker.app and then defining /usr/bin/milkytracker:

Code: [Select]

#!/bin/sh
find /lib | grep libGL || export NO_OPENGL=1
milkytracker
However, these overrides would jail the user into those settings forever  ...

I'd like to share a few thoughts here:
1. Without libGl, the program fails. The script tests for and handles that.
2. With libGl, the program works. The script tests for and handles that.
3. The export is not system wide. It only exists for that instance of milkytracker.
4. If libGL gets installed while milkytracker is running, exit and restart milkytracker.

I don't see a forever here.

If someone wishes to edit a script, they can replace the link
with a copy of the file it points to:

Code: [Select]

sudo busybox cp /Path/To/Link/LinkName /Path/To/Link/
If they want that file to persist between reboots, they can add
it to their backup.

60

Release Candidate Testing / Core v17.1beta1

« Last post by Juanito on June 22, 2026, 10:01:29 AM »

Team Tiny Core is pleased to announce that Tiny Core 17.1 Beta1 is available for public testing:

http://repo.tinycorelinux.net/17.x/x86/release_candidates/distribution_files
http://repo.tinycorelinux.net/17.x/x86_64/release_candidates/distribution_files

This is an beta level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.

We appreciate testing and feedback.

Changelog for 17.1 beta1:
* update kernel to 6.18.35
* update zsync - thanks to @GNUser

Note that you will need the updated kernel module extensions from the appropriate repo - it is probably better to download the ones you need prior to updating rootfs*gz, modules*gz and vmlinuz* and rebooting.