Tiny Core v4.0

[roberts]

Team Tiny Core is proud to announce the release of Tiny Core & Micro Core v4.0.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/release

Change log:
* Updated kernel to 3.0.3
* Updated udev to 173
* Updated glibc to eglibc-2.13
* Updated e2fsprogs base libs to 1.41.14
* Updated gcc base libs to 4.6.1
* Updated util-linux base libs to 2.19.1
* Updated eglibc for 486/586 support.
* Updated base Xlibs (microcore users need to get new Xlibs.tcz)
* Updated all the custom core utilities to use the new repository area.
* New loadcpufreq to handle module loading.
* Updated ondemand for console based extensions via Freedesktop Exec=cliorx prgname
* Updated tce-load & tce-audit for dynamic KERNEL dependency processing.
* Adjusted .xsession to handle X startup failure.
* Adjusted .setbackground colors for wallpaper handling.
* Updated AppBrowser Search and Keyword as described below.
* Updated ab Search and Keyword.
* Updated search.sh internal script support for new search method shared by AppBrowser & ab
* New keyword.sh internal script support for new keyword method shared by AppBrowser & ab
* Updated loadcpufreq ( C rewrite for speed)
* Updated busybox 1.19.2 with latest patches and nbd-client
* Updated rebuildfstab, tc-config, & rc.shutdown for nbd-client support.
* Updated getTime.sh for random selection of time servers (atl chi sj).
* Updated Luxi fonts to disable hinting.

Notes:
The Search method for both AppBrowser and ab is now a local info.lst search.
To use enter the starting few characters of the desired extension, e.g., abi for abiword, or ope for opera

Both AppBrowser and ab now offer Keyword searching.
Examples: enter browser to display browsers, enter game to list games.

The following has been deprecated in the 4.x series:
* Floppy Tool (floppytool.sh & fdtool)
* Starter Packs (loadpack & loadpack.sh)
* Hybrid Mode (boot local & mktclocal)

The new repository areas:
 http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/

Attn: Micro Core users will need new wbar.tcz, Xlibs.tcz, and Xprogs.tcz from 4.x repository.

[bmarkus]

Does it mean EOL of 3.x line?

Sent from my ZTE-BLADE using Tapatalk

[bigpcman]

I have installed tc 4.0 and am running it now. This post is from a vnc remote connection to my TC 4.0 server.
Looks good so far. Great work team tinycore! 

[meo]

Hi TC members!

This is my first test running the stable TC 4.0 and everything seems good so far. A big hand to the TC team making this possible!!!

Have fun running this new and heavily updated version of TC,
meo

[bmarkus]

What is the status of compiletc toolchain, regarding the 10-15% executable size increase? Updating extensions on 4.0 would bring unnecessary size increase, but do not want to use 3.8 for building. Maybe a temporary fix to keep GCC from 3.8 

[curaga]

GCC was rebuilt with the frame-pointer option turned on, current 4.x toolchain should create normal sized executables again.

[bmarkus]

GCC was rebuilt with the frame-pointer option turned on, current 4.x toolchain should create normal sized executables again.

Confirmed ! 

[okmijn666]

new wersion ?

EXELLENT Thanks to all dev's !

[Arslan S.]

where is tcl 4.x linux source and config ? so we can compile some modules

[roberts]

Does it mean EOL of 3.x line?

Sent from my ZTE-BLADE using Tapatalk

Yes.

[bmarkus]

GCC was rebuilt with the frame-pointer option turned on, current 4.x toolchain should create normal sized executables again.

gnutls is even smaller, 483k -> 471 k with same build script!

[bmarkus]

A while ago it was decided to drop openssl-0.9.8 and move to 1.0.0 How do we proceed?

Just built bind against 1.0.0 static. It's OK, but in general I prefer shared libs to reduce size and do not want to maintain dependencies.

[Jason W]

openssl-0.9.8 has not been dropped, it is still the standard shared openssl.  The static openssl-1.0.0 was made available for folks who want to build their apps against the latest openssl, without causing conflict with the shared openssl-0.9.8. 

The benefits of going static with openssl is we never have to have a repo wide rebuild to accomodate an openssl upgrade.  Or at least it buys us time until we want to rebuild everything against a new latest shared openssl. 

Perhaps with TC 5.0 will be a good time to start from scratch, with by then a gtk3, python3. openssl-1.x, etc.  With openssl being the only thing that needed a repo wide rebuild, and it affects the most extensions of any of the three libs mentioned above, we are just staying with 0.9.8 for the shared lib.  For now, smaller size versus latest and greatest, the extension maker has a choice. 

But to be honest, I personally like the idea of a static openssl since then we would never have to rebuild the entire repo for an openssl upgrade.  The cost being extension size.  Further discussion can take place in the thread below:

http://forum.tinycorelinux.net/index.php/topic,11058.0.html

[andrewb]

Are there any files that may be backed up that need to be modified / removed when upgrading a 3.8 installation to 4.0?


Just a suggestion, but maybe a standard section in any release announcement could be files that will be affected that amay be in the backup, e.g. in the announcement of 3.7 there was:

Note: Files that have changed and are likely in your backup:

Perhaps 'Files that have changed and are likely in your backup:'  could be made a standard section, even if it just stated 'None'. This way users could be sure that the issue of files in the backup isn't overlooked when upgrading.

[maro]

I just noticed that the downloads page is still pointing to the v3.8.4 images. I'd imagine as soon as the MultiCore ISO has joined it's "siblings" those links will be adjusted accordingly.