Tiny Core v17.0

[Juanito]

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

Changelog for 17.0:
* kernel updated to 6.18.2
* glibc updated to 2.42
* gcc updated to 15.2.0
* binutils updated to 2.45.1
* e2fsprogs base libs/apps updated to 1.47.3
* util-linux base libs/apps updated to 2.41.2

* provides.sh: Update scripts to work with https mirrors from mbartlett21
* tce-update: Undo changes around fetchzsync from mbartlett21
* tc-functions: Update https checking from mbartlett21
* tc-functions: Change subshell from mbartlett21
* update-everything: Add /usr/local/bin to PATH from mbartlett21
* shutdown.sh: handle empty lines in /opt/.xfiletool.lst from mbartlett21
* 50-udev-default.rules: expanded input device permissions from bdantas

[Stefann]

No reactions after a week.
Just want to say: super thanks!
This week is quite busy, no time for updates.
Next week I will update my hp510 thin client with Via Eden dual core 1G 64bit processor.
If that is succesfull my ultra low power Via Eden 500MHz single core 32bit system will follow.
The latter is running my home control system so I need to be a bit careful. The first I use as staging system.

Having said that…
What is best way to upgrade?
Do I need to make a new usb installer and start from scratch?

Last time I just copied core.gz and vmlinuz. That would however not do anything with modules.gz.
I actually also donot know what modules.gz is good for.

I’m running tinycore in frugal mode booting from internal compact flashdrive.

[Juanito]

core.gz = rootfs.gz + modules.gz

You can replace core.gz and vmlinuz to update, but I would recommend using a different tce folder so that you don't have problems with old extensions that are no longer compatible.

[Rich]

Hi Stefann

... You can replace core.gz and vmlinuz to update, ...

In addition, you will need to replace any kernel module extensions you
are using, for example:

Code: [Select]

alsa-modules-KERNEL.tcz
filesystems-KERNEL.tcz
graphics-KERNEL.tcz
i2c-KERNEL.tcz
wireless-KERNEL.tcz
etc
Where the  KERNEL  part looks something like  6.12.11-tinycore.

A better plan would be to create a new tce directory as Juanito
suggested and download new copies of all of your extensions
from the TC17 repo.

You can simplify the process if you  cd  to the tce/optional/
directory you want to clone.
Then:

Code: [Select]

ls -1 *.tcz > Ext.lstThat's a  dash one  after  ls.
Move the  Ext.lst file to your new  tce/optional/  directory.

Grab a copy of the latest  FetchExt.sh  script from here:
https://forum.tinycorelinux.net/index.php/topic,23034.msg178902.html#msg178902
Place it in your new  tce/optional/  directory and make it executable.
Read the  Define Variables  section of the script, or run:

Code: [Select]

./FetchExt.sh -h
For  Intel  type processors run this:

Code: [Select]

KString="\-[0-9]+.[0-9]+.[0-9]+-tinycore.*.tcz"
sed -i -E 's|'$KString'|-KERNEL.tcz|g' Ext.lst
For  Arm  type processors run this:

Code: [Select]

KString="\-[0-9]+.[0-9]+.[0-9]+-piCore.*.tcz"
sed -i -E 's|'$KString'|-KERNEL.tcz|g' Ext.lst
Then run:

Code: [Select]

for F in $(cat Ext.lst); do ./FetchExt.sh "$F"; doneThat should populate your new  tce/optional/  directory with new
versions of all of your extensions.

[Stefann]

oops...
Thanks @rich...
however... I found some time and already started.

On my HP510 thin client with Via Eden 1GHz dual core 64bit processor
Im using the 32bit iso because this is the staging system for my ultra low power Via Eden 500MHz single core 32bit system
Its a frugal install from the internal compact flash
Its a headless system reachable by ssh & VNC with samba file-service

What I did:
1/
- download the core-17.0.iso to my MacBook
- copied core.gz to /mnt/sda1/tce/boot/core17.gz
- copied vmlinuz to /mnt/sda1/tce/boot/vmlinuz17
- changed /mnt/sda1/tce/boot/extlinux/extlinux.conf to boot from core17.gz & vmlinuz17
sudo reboot

==> succesfull!
==> both ssh & VNC connection work, samba works

2/
made copy of the tce/optional folder to make sure I can revert back.

3/
Using the VNC gui:
- apps, update
- process
wait about 10 minutes.
==> All successfully updates BUT some apps require python3.14 (was running on 3.9, coming from TC15)

4/
installed python3.14.tcz
==> success

5 (still to be done)/
Now I need to update some python3.9 modules I installed myself, will do that later

Question: so far so good? or do I need to revert back to step 2 and follow your guidance?

[Rich]

Hi Stefann

... Question: so far so good? or do I need to revert back to step 2 and follow your guidance?

Sounds like you have it under control.You said you ran
apps, update. There's an  update-everything  command
that handles it all in one shot.

[Stefann]

Thanks!

Yes I updated all in one go.
Used the corebook to help me.
In “normal live” I work from the commandline by ssh. But for these update things I like using the gui for reason it requires me to do a lot of things I very rarely do. And be aware that I’m absolutely not an expert.
The reason I asked is that I only marginally did understood your guidance.
And… I prefer understanding what I do, as that helps a lot when things go wrong.
Still thanks. I did reread it 5 times and I think I start to understand it (lol). Learning is fun.

So…
I did the apps update from the gui.
As indicated by the corebook you can select all apps together by selecting the first, holding shift, and selecting the last.


All in all….
I’m doing a much better job than last year. TC15-to-16.
Last year I only updated core.gz and vmlinuz. I was totally not aware that I should have done something with the apps. The initial reply from @juanito did guide me to that (thanks).

It’s all a bit tricky as the systems are headless. So if I loose them I have to physically unmount them and get a keyboard and monitor from the attic.