Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: qopit on September 09, 2016, 11:47:49 AM
-
I'm trying to put together some older 6.x and 7.x corepure64 images, and vmlinuz64 is missing from these locations:
http://www.tinycorelinux.net/7.x/x86_64/archive/7.0/distribution_files/
http://www.tinycorelinux.net/7.x/x86_64/archive/7.1/distribution_files/
vmlinuz64 is occasionally there in older releases, like these:
http://www.tinycorelinux.net/6.x/x86_64/archive/6.4.1/distribution_files/
http://www.tinycorelinux.net/6.x/x86_64/archive/6.0/distribution_files/
but vmlinuz64 presence is inconsistent. eg: it isn't in the dirs for 6.1, 6.2, 6.3, or 6.4.
Where is the best place to get the vmlinuz64 file for the matching version? Will the release (vs archive) folder's copy of vmlinuz64 be 100% consistent across minor revision bumps?
-
Also, since I'm asking about release and archive folders... when building images it is a bit tricky that the latest version number doesn't have a direct path that I can see. For example, to get 7.2 files I currently need to go to release/, whereas for 7.1 and 7.0 I go to archive/. For example, the rootfs.gz file paths for 7.0, 7.1 and 7.2 are, respectively:
http://www.tinycorelinux.net/7.x/x86/archive/7.0/distribution_files/rootfs.gz
http://www.tinycorelinux.net/7.x/x86/archive/7.1/distribution_files/rootfs.gz
http://www.tinycorelinux.net/7.x/x86/release/distribution_files/rootfs.gz
with 7.2 being in "release/" because it is currently the latest version.
Is there a different location to pull direct version paths? PostgreSQL, for example, has a direct download path for every version tick, including the latest release:
https://www.postgresql.org/ftp/source/
Having each tick available is really convenient for automated build scripts.
-
vlinuz64 was only archived when it changed
-
The archives are scripted, so they'll be consistent. There's no versioned path for the latest release, I'm afraid. If you need to query the latest version, see the file "latest".
-
Does the "only archived when it changed" rule apply for the modules64.gz and rootfs64.gz files?
Also... where is the "latest" file? I couldn't find it in the repos.
-
modules64.gz is only archived when it changes, but rootfs64.gz changes every time.
The "latest" file is only implemented for x86, but it could be implemented for x86_64 if required I guess.
-
In the top directory of any mirror.
http://repo.tinycorelinux.net/latest for example.
-
CorePure64-current.iso and TinyCorePure64-current.iso symlinks added