Tiny Core v6.3

[Juanito]

Team Tiny Core is proud to announce the release of Core v6.3:

http://www.tinycorelinux.net/6.x/x86/release
http://www.tinycorelinux.net/6.x/x86_64/release

Changelog for 6.3:
* tce-load: exit if fromwhere doesn't exist
* tc-config: nfs4 patch from gerald_clark
* tce-load: separate the listing and handling loops, patch from aswjh
* tce-audit: fix adding missing extensions to tce_lst
* tce-setup: move extension loop to tce-load, 4% speedup in CorePlus tce-setup time from aswjh
* tce-load: simplification by aswjh
* tce-load: simplify app_exists by aswjh
* tce-load: -t TCEDIR patch from aswjh

Note also that Xvesa/Xfbdev included in TinyCore and CorePlus and the Xfbdev in TinyCorePure64 have been updated to the latest repo version

[pq5190362]

Team Tiny Core is proud to announce the release of Core v6.3:

[...]

Changelog for 6.3: [...]

May I ask why you are still using kernel 3.16.6?

Kernel 3.16.6 is outdated. And even kernel 3.16.7 is outdated. Only Canonical provides some security updates for it AFAICT, see: http://en.wikipedia.org/wiki/Linux_kernel#Maintenance.

Why don't you also update the kernel?

As far as I can tell, the kernel only seems to be updated with each major Tiny Core Linux release.

But why?

Couldn't you have updated the kernel to at least kernel 3.18.x (current LTS kernel) with Tiny Core Linux 6.3?

And have you actually patched kernel 3.16.6 with some security fixes? Or have you left it as is?

Regards

[curaga]

TC has a partial embedded focus, not changing the kernel from under users has benefits. Anything from no new regressions to not invalidating custom kernel modules. Upgrades of Core are supposed to be safe and easily applicable.

Of course TC will work with custom kernels just fine, in case you require 4.1 or any other such version. If you run a security-conscious service, such as a public server, you should consider RHEL/CentOS.

[pq5190362]

Of course TC will work with custom kernels just fine, in case you require 4.1 or any other such version.

And would graphics-3.16.6-tinycore.tcz still work with kernel 4.1?

Regards

[curaga]

No, you need to build matching modules.

[pq5190362]

No, you need to build matching modules.

Thanks for your reply.

One more question:

Would you then have to package those modules as an extension and name it graphics-4.1.tcz?

I am asking because:

xf86-video-intel.tcz
xf86-video-nouveau.tcz
xf86-video-ati.tcz
etc.

all have:

graphics-KERNEL.tcz

in their dep(endency) file.

Regards

[Juanito]

It would need to be graphics-4.1-tinycore.tcz or graphics-4.1-tinycore64.tcz.

Or, alternatively, you could call it anything you like and adjust the relevant *.tcz.dep files locally to suit.

[coreplayer2]

Seems like very few idle hands at Linux/kernel/git/firmware lately, so..  So am taking the opportunity to update some firmware extensions.

many updates to WiFi, Bluetooth and audio firmware, coming soon

[core-user]

many updates to WiFi, Bluetooth and audio firmware, coming soon

Would it be possible to have the rt74 (rum under BSD) wifi driver available, thanks for your time & work.

[coreplayer2]

many updates to WiFi, Bluetooth and audio firmware, coming soon

Would it be possible to have the rt74 (rum under BSD) wifi driver available, thanks for your time & work.

I'm not familiar with rt74..  perhaps you have a hardware ID???

[core-user]

Sorry for the delay, (I couldn't find this post again), it should be rt73.bin.

[Xianwen Chen]

On the front page, the header for the 6.3 release is "6.2". You may want to correct that.

[curaga]

Fixed, thanks for reporting.

[coreplayer2]

Sorry for the delay, (I couldn't find this post again), it should be rt73.bin.

Ah ok ..  already done, just needs submitting, by the weekend at least

Code: [Select]

firmware-ralinkwifi/usr/local/lib/firmware/rt73.bin

[core-user]

Thankyou.