Core v4.7.1

[roberts]

Core v4.7.1 is now posted. This is a minor bug fix and adjustments release.

Change log:

• Updated Apps GUI to fix missing buttons on Selective Copy to File System.
• Updated tce-load - added -f option to force overwrite of existing items. Use with caution.
• Updated tc-functions - added support for arm builds.
• Updated tce - cleanup display when no .dep or .tree files exist.
• Updated ondemand - try to execute already loaded CLI items.

Note: Requires updated Xprogs.tcz

Special Note: Because of the situation on ibiblio, no available disk space. I am forced to host these files elsewhere. I understand that it will not be as easy or convenient to upgrade. It is beyond our control if or when the ibiblio matter is resolved. Your understanding and patience is appreciated.

The files are available at: http://code.google.com/p/tinycore-x86/downloads/list

[aus9]

I appreciate the team has a number of issues regarding the repository

any chance that when you get some spare time, the google site includes some md5sums please?

and extra request, because I am selfish, any chance you could upload the core and kernel and their md5sums as well?

thanks heaps

[gerald_clark]

Core and kernel are in the iso.  Just mount it.

[roberts]

For ease of upgrading, I have posted the kernel and core.gz.
http://code.google.com/p/tinycore-x86/downloads/list

[aus9]

thanks heaps

[yoshi314]

there is some glitch in scmapps, when attempting to check for updates :

"you are running 4.7.1 . The latest release is 4.7"

i assume it's related to the mirror situation ?

[curaga]

Yes, the latest version check is done on ibiblio, and the latest version on ibiblio is 4.7. Please ignore it for now.

[roberts]

there is some glitch in scmapps, when attempting to check for updates :

"you are running 4.7.1 . The latest release is 4.7"

i assume it's related to the mirror situation ?

I keep hoping for a miracle, but not seeing one...
I have updated the webpage on ibiblio to reflect that the latest relesee is 4.7.1.
I have updated the download page to redirect to Google Code.

[genec]

I understand that it will not be as easy or convenient to upgrade.

1) Although it is possible to provide direct links, the SHA1 checksums would not be seen
2) I'm not sure the opinion of the community at large but I've regarded MD5 checksums as a borderline integrity check due to the computational feasibility of a collision.  I don't know how computationally feasible it would be to have a collision and pass decompression checks.  I certainly welcome seeing SHA1 checksums for the ISOs.

[curaga]

FWIW, sha1 sums are embedded in the zsync files. If you download via zsync, it checks that for you - if not, you can view the .zsync file in a text editor.

Not sure if those were posted to google code though.


That said, I still would trust md5sum. Being able to get a collision - sure. But to do that so that the compression is still valid ups the ante a lot.
I do believe that's possible. However, doing that without significantly changing the file size, that feat I do regard as improbable enough.

If there was a TinyCore iso at 37mb, that should raise a red flag

[roberts]

Please note that, hopefully, Google Code will be a very temporary solution.

[genec]

Aside from space to spare, Google also has a lot bandwidth to spare.

[roberts]

As reported by SamK, a new cut of TinyCore iso is now posted on Google Code. See:
http://forum.tinycorelinux.net/index.php/topic,14507.msg82168.html#msg82168

This issue only involves the TinyCore.iso and was the result of renaming the fltk library.

[Juanito]

was core64 updated to 4.7.1?

[roberts]

Yes. core64 shares the same base as core with only the modules being different.