Tiny Core Base > Corepure64

Corepure64 v5.1

<< < (5/5)

coreplayer2:
After release, I believe the intention is to use only files from  http://tinycorelinux.net/5.x/x86/release/

I think release candidates are normally pulled once release goes public, at least until candidates for a new potential release are available for testing.  In any case we should definitely not mix modules from release http://tinycorelinux.net/5.x/x86/release/  with any files from  http://tinycorelinux.net/5.x/x86/release_candidates/

I think you'll find instructions/notes from the announcement page helpful http://forum.tinycorelinux.net/index.php/topic,16293.0.html

Distribution files are for those who wish to build custom configurations.  There is no "core.gz" for x86_64 or corepure64, so you would need files from http://tinycorelinux.net/5.x/x86/release/distribution_files/  only.


From http://tinycorelinux.net/5.x/x86/release/distribution_files/  use
For x86_64 (with 32bit userspace)
rootfs.gz
modules64.gz
vmlinuz64

For x86_64 (corepure64)
rootfs64.gz
modules64.gz
vmlinuz64


Hope that's clearer

Juanito:
In fact the files at http://repo.tinycorelinux.net/5.x/x86_64/release_candidates/ were outdated.

I've updated the files to 5.2rc1 and will try to remember to delete the files when there are no release candidates for testing in order to avoid confusion.

'Happy to hear that you got things working  :)

Juanito:
In case it helps users try out corepure64, iso created at:

http://repo.tinycorelinux.net/5.x/x86_64/release/CorePure64-5.1.iso

killerhippy:
Happy me indeed!

At this point want to say thank you for your good work. Don't mind about errors, they happen, all is human  ;)

From my point of view, a "release" is a publication.
A "release candidate" then is a "to be released", right?
I didn't think about it until now.

Before I thought, a "relase candidate" is the newest version and so the "release" version was older - which isn't correct.

Navigation

[0] Message Index

[*] Previous page