Tiny Core v17.1

[Juanito]

Team Tiny Core is proud to announce the release of Core v17.1
http://www.tinycorelinux.net/17.x/x86/release
http://www.tinycorelinux.net/17.x/x86_64/release

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.

[CNK]

Core-17.1.iso is an empty file (zero bytes).

[Rich]

Hi Juanito
How about that. It even says zero bytes here:
http://www.tinycorelinux.net/17.x/x86/release/ 

[Leee]

I am -so- glad I was busy/lazy today and didn't get around to the install yet.  There's no  telling how long it would have taken me to figure that out.   

[Chinaboy5216]

Hi All,

sorry to barge in, I'm currently on 17.0 and would like to upgrade to 17.1 but as brand new user have no idea how to do this.

Would there be a step by step guide available for this? Don't want to ruin my good old eeepc 701sd.

Many thanks in advance, really like Tiny core a lot, it brought my oldie back to life

[Rich]

Hi Chinaboy5216
Before updating kernels, you should download updated versions of
kernel modules you are using:

Code: [Select]

getMirror
cd /etc/sysconfig/tcedir/optional
for File in *\-6.18.2\-*.tcz*; do wget $MIRROR/${File/\-6.18.2\-/\-6.18.35\-}; done
Then you can download and boot updated vmlinuz and core.gz files:
http://www.tinycorelinux.net/17.x/x86/release/distribution_files/

[Chinaboy5216]

Hi Rich,

Thank you for your help, I will try after doing a backup and well if it doesn't work can always reinstall tiny core.

Thanks mate, much appreciated.

[Juanito]

Core-17.1.iso is an empty file (zero bytes).

Hmm - some fat fingered typing - it should be alright now.

[Leee]

I haven't done a lot of research on this but on Tiny Core 17.1 on x86-64, configured exactly as with Tiny Core17.0 on x86_64, the clock in the jwm tray does not update.  I didn't notice this issue in 17.1-beta, though I might have simply missed it.

Unrelated: Lightning strike just about knocked me out of my chair while I typed that - I think I'll shut down for a while.

edit: Never mind - I'm seeing the same in 17.0/x86-64 now, so it looks like I've broken something.

[Rich]

Hi Leee
First make sure the system time is working:

Code: [Select]

tc@E310:~$ date; sleep 3; date
Sat Jul 18 09:19:33 UTC 2026
Sat Jul 18 09:19:36 UTC 2026The 2 times reported should be 3 seconds apart.

Next, check your jwm config file (~/.jwmrc). Check any StartupCommand
and Clock* entries to make sure any clock related scripts or programs are
both present and running.

[Leee]

Hi Leee
First make sure the system time is working:

Code: [Select]

tc@E310:~$ date; sleep 3; date
Sat Jul 18 09:19:33 UTC 2026
Sat Jul 18 09:19:36 UTC 2026The 2 times reported should be 3 seconds apart.

Next, check your jwm config file (~/.jwmrc). Check any StartupCommand
and Clock* entries to make sure any clock related scripts or programs are
both present and running.

The problem, as usual, turned out to be one of my own making.  And it was two or three days old.


Instead of a single <Clock> tag in .jwmrc-tray, displaying both the date and time, I had I had split it into two separate <Clock> tags, one for the date and one for the time, so that I could attach different <Button> tags to each.

It turns out that, if there are multiple <Clock> tags, only the first one updates - so the "date" one would have updated correctly but, of course, only once per day.  I had made this change a couple of days ago and very carefully tested that both were displayed and the right, middle and left <Button> actions worked for each <Clock> tag but never noticed that the time was not ticking off the seconds.

Upon review, the jwm docs do mention something about having only one <Clock> tag.