Updating tinycore, where is the version (7.x,8.x,9.x) defined ???

[binär]

Let´s say I do a tce-update, the script checks tinycore repository for updates.
The repository URL itself is defined in /opt/tcemirror
But where is defined the architecture, version for downloading updates ?
It´s at least not in this tce-update script nor in any tinycore-specific script I could find.
I´ve read the Tinycore book "into the core" but this information is not there.
any idea ?

[bmarkus]

Architecture comes from kernel, for TC version see version command.

[binär]

Thank you for your quick answer !
So, how do I change the version, and which scripts are using this version command, please ?

[bmarkus]

Why do you want to change version??

[binär]

Because I want to bend Tinycore to my will, I guess.
So, it´s solved, I found out what was going on:

- most tinycore-specific scripts source /etc/init.d/tc-config where a good deal of functions are defined.
the interesting ones are
            getMajorVer: gets the major number of the release, from the /usr/share/doc/tc/release.txt  (yep. convoluted)
            getBuild: gets the platform from uname -m (x86, ARMv6, ARMv7, x86_64)
            getMirror: assembles the updare URL from /opt/tcemirror, getBuild and getMajorVer
- the tce-update script uses getMirror to perform the update. It cannot update to a new version.

So just by changing the major version number in /usr/share/doc/tc/release.txt I can upgrade to another major version release with tce-update.

[bmarkus]

So just by changing the major version number in /usr/share/doc/tc/release.txt I can upgrade to another major version release with tce-update.

It is not true.

[Rich]

Hi binär

Because I want to bend Tinycore to my will, I guess. ...

 ... So just by changing the major version number in /usr/share/doc/tc/release.txt I can upgrade to another major version release with tce-update.

It would be safer to do a fresh install and use your old  onboot.lst  as a reference for installing wanted extensions. Dependencies
get re-factored so some extensions may disappear and be replaced by one or more new ones. By using your old  onboot.lst
as a reference you're updating "parent" extensions and allowing TCs install tool to resolve dependencies.

Your plan will result in all extensions (that can be found in the new repo) being replaced because the MD5s won't match. Then to
complete the process you need to reboot preferably into a matching kernel and initrd. You may also find kernel specific extensions
don't get updated because your old kernel version is not listed. Chances are you'll just be creating lots of problems for yourself.

[binär]

Well I found this to be a convenient, unorthodox solution.
The kernel (RT_PREEMPT 4.20.0 on BeagleBone Black) and the image derivates from piCore with some needed customizations.

While I understand it´s not what the tce-update script is intended for, it worked enough for me. I´d rather have a proper config file for the tinycore version, (like for example source.list for debian) but unfortunately Tinycore
has its bits scattered everywhere (like within / and /usr/local),
or even sometimes has dupes (like kernel modules)
there is no consistency between the packages / platforms / version (like for example dropbear is present into armv7 until v7.x included, but disappears from v8.x
and worst of all, there is a mess of documentation (confused, outdated, in different places)
and no proper tools for remastering, it took me a while to figure out what config options exactly were needed to configure a kernel to load a tinycore image.

That said I like the simplicity, modularity of Tinycore as well as the philosophy running the whole system from RAM as well as the flexibility of the extensions. This allows me to make a bare system for a given platform, and to quickly morph it into whatever I want. Without going all the way from compiling everything into an image like yocto + angström linux

[coreplayer2]

While I understand it´s not what the tce-update script is intended for, it worked enough for me. I´d rather have a proper config file for the tinycore version, (like for example source.list for debian) but unfortunately Tinycore
has its bits scattered everywhere (like within / and /usr/local),
or even sometimes has dupes (like kernel modules)

I disagree.   I think you'll come around when you understand the file system..

And then, almost everything you need to know about your TC install you'll find here

Code: [Select]

/etc
/etc/init.d
/etc/sysconfig
/usr/bin/tce-*
/usr/local/tce.installed
cat /proc/cmdline

For version info try here

Code: [Select]

/etc/os-release
/usr/share/doc/tc/release.txt


[curaga]

there is no consistency between the packages / platforms / version (like for example dropbear is present into armv7 until v7.x included, but disappears from v8.x

Extensions are user contributed.