Tiny Core Base > Final Releases

Tiny Core v17.0

<< < (2/3) > >>

Rich:
Hi Stefann

--- Quote from: Stefann on February 16, 2026, 10:31:28 AM --- ... Question: so far so good? or do I need to revert back to step 2 and follow your guidance?
--- End quote ---
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.

thane:
I agree that burning a new 17.0 ISO DVD would have been the cleanest approach (which is what I've done in the past for major upgrades), but when I tried a found my last DVD burner has had it. So basically did what's suggested here (replaced core.gz, vmlinuz, kernel extensions, and did an update everything). Also did an update .dep files and found I had a couple of missing dependencies, and cleaned out a few that don't seem to be needed anymore. Working OK so far, but yes it wouldn't surprise me if there's a few loose ends...

thane

GNUser:

--- Quote from: Stefann on February 16, 2026, 02:07:19 AM ---What is best way to upgrade?

--- End quote ---
This is the way I do it, in 4 easy steps:

While running the old version of TCL (e.g., TCL16):

1. I replace /boot/corepure64.gz and /boot/vmlinuz64 with the new version from TCL17

2. I find the extensions that need to match the kernel version:

--- Code: ---$ cd /etc/sysconfig/tcedir/optional
$ find . -name "*$(uname -r | sed 's/-.*//')*"
--- End code ---
I write down the above extensions on a piece of paper

3. I use Rich's  FetchExt.sh  script to download the new kernel-version-specific extensions into the  optional  directory. Make sure the  TC  and  ARCH  variables at the top of the script are correct (TC should be the new version that you are upgrading to) (FetchExt.sh can be obtained here: https://forum.tinycorelinux.net/index.php/topic,23034). For example:

--- Code: ---$ cd /etc/sysconfig/tcedir/optional # if you just did step 2 above, you are already in the correct directory and don't need to do this  cd  again
$ FetchExt.sh graphics-KERNEL ipv6-netfilter-KERNEL # just an example--fetch all the extensions that you wrote down in step 2

--- End code ---

At this point (with new corepure64.gz, new vmlinuz64, and new extensions that need to match the kernel version), you can go ahead and reboot. A normal reboot is all you need--you'll be running the new version of TCL after the reboot :)

After rebooting into the new version of TCL (e.g., TCL17):

4. When booting is complete, you just need to update the rest of the extensions (i.e., the non-kernel-version-specific ones), which can be done easily enough with one command:

--- Code: ---$ update-everything
--- End code ---

Stefann:
Thanks all!

I'm learning a lot.

So basically:
- replacing core.gz & vmlinuz is enough to have the new linux version after reboot.
But....
- IF one is running kernel specific tcz extensions things will/may fail at reboot
So...
- One needs to make sure that any kernel specific tcz extensions are updated BEFORE reboot
---> kernel specific tcz extensions are recognised because their name ends with -#.#.#-tinycore with #.#.# being the kernel version.
---> update canNOT be done with the normal apps-update method because that updates *.tcz extensions to current kernel version and the objective is to update to the "kernel version after reboot".
---> update needs to be done with the fetch script made by Rich as referenced by both Rich & GNUser in previous posts.

After reboot linux is updated, but applications not yet.
- update applications after reboot:
---> either by the appstool in the guy
---> or by the tce-update command from command line

And while the above is enough to update, before doing the update:
- one may want to rename & keep the previous core.gz and vmlinuz
- one may want to copy the tce/optional directory to a backup location

Unrelated:
I'm happy to find python3.14 in TC17! I was still running 3.9 and already run into situations that a newer version was required.
It may have been in TC16 without me noticing because when I upgraded to TC16 last year I was not aware I should have done an application update as well.
So: thanks Juanito!

And also:
- I can confirm TC17 32bit x86 runs on Via Eden 1GHz dual core 64bit processor
(using 32 bit core.gz because this is staging system for my 32bit via eden system)

Navigation

[0] Message Index

[#] Next page

[*] Previous page