Core v4.4

[roberts]

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

The major theme for Core v4.4 is kernel & modules update and improved extension searching via tags.

Changelog for 4.4:

* Minor kernel update to 3.0.21 to support the following:
** ax25 / ham radio support
** kexec
** efficeon agp patch
** r6040 mii fix
** isa libata enabled for very old laptops
** xts, gf128mul for truecrypt uses
** resolves the kernel panic issue when mounting CIFS shares.
* Updated tc-config with syslog/rsyslog patch
* Updated Xprogs.tcz: scmbrowser and smc-fetch.sh tweaks
* Updated search.sh added -t option for tag search.
* Updated provides.sh for CLI use.
* Updated appbrowser for new tag search.
* Updated ab keyword is now a tag search.
* Updated tce-size with date check on sizefile update.
* Updated tce-setup fixed when base boot code is used with missing /tmp/tce/optional directory.
* Updated tce-setdrive with a required readlink.
* Updated filetool.sh with a required readlink when used after tce-setdrive.
* Recompressed modules to save space.
* Added ssb module to base.
* Updated busybox 1.19.4 plus patches to fix busybox tftpd vulnerability.
* Updated tc-terminal-server to accomodate busybox tftpd vulnerability.
* Updated scm-search -t for tag searching.
* Updated scmbrowser for tag searching.
* Updated filetool.sh improved invalid device handling.
* Updated tce-setdrive now sets default backup device without a reboot.
* New boot code, e.g., iso=sdb1 booting from a single ISO file to load embedded extensions.
* New fromISOfile script for after boot support of a single ISO file embedded extensions.
* Updated rebuildfstab fixed pid checking.
* Updated exittc and filetool spelling.


Update instructions, from the release distribution files area:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/distribution_files/
1. Copy over new vmlinuz
2. Copy over new core.gz
3. boot into new system

if You have/use X then
AppsAduit -> Dependencies -> Build Reporting Database -> Fetch Missing

or if you only use Core (no X) or Xorg did not start and only have a system prompt use:
tce-audit builddb
tce-audit fetchmissing


Note: Xprogs.tcz has been updated and is now in the repository.

[vinnie]

Mythical! I'll update in a few days!

[meo]

Hi Tiny Core Team!

The new release is awesome! I'm running it now. Thanks a lot for your hard work putting it together.

Have fun making the TC community happy,
meo

[coreplayer2]

This build is sweet thanks

I really appreciate the effort gone into equipment compatibility, thank you.

[redwolf]

I was having trouble getting the newest version to boot.  My TCE is on a RAID, LUKS, LVM.  I finally realized that it was failing to mount the raid array due to raid-dm-3.0.21-tinycore64.tcz not being present.  It was only then that I realized the kernel version had changed. 

I could have sworn I'd tried updating dependencies as you suggested, but I ended up installing raid-dm-3.0.21-tinycore64.tcz while booted into tce=pre.

Anyway, it's almost working now, but there doesn't seem to be an nvidia-module-3.0.21-tinycore64.tcz in the repository.

Out of curiosity...why 3.0.21 instead of 3.0.3 this time?

Thank you for all the effort you all put into Tiny Core.  I love this operating system.

[GoodGuy98]

I tried to update to update a flash drive from v4.3 to v4.4 following the instructions.

1. Copy over new vmlinuz
2. Copy over new core.gz
3. boot into new system

When I rebooted, Xorg did not start, so I ran:

tce-audit builddb

It produced the following error message

Building extension database from /etc/sysconfig/tcedir/optional

mv: can't preserve ownership of 'tce.lst' operation not permitted

My video driver is using nVidia in case that makes a difference.

[roberts]

Likely your using a file system that does not support permissions.
Likely in this particular case that it does not matter.

[Rich]

Hi redwolf
The maintainer of the   nvidia-module   extensions is currently serving his country and not due back until mid May.
The kernel was bumped to a higher version due to some problems with 3.0.3.

[solorin]

Thank you and congratulations to the Tinycore Team on another amazing release.

I tried to update today, but the audio turned out to be a bit wonky.

OSS installs OK but complains: depmod: ./kernel.tclocal: No such file or directory.

Is it something I should be concerned about? I am in the midst of exploring a lot of audio in Tinycore,
so I'd like to tune it solidly.

Cheerio,
solorin

[Rich]

Hi solorin
I don't know how much I can help with this, so I'll just ask the obvious.
If you enter  ls -l /lib/modules/3.0.21-tinycore
Does it contain the entry  kernel.tclocal->/usr/local/lib/modules/3.0.21-tinycore/kernel
If it does, then the extension may be making a reference to  /lib/modules/3.0.3-tinycore  which no longer exists.

[bmarkus]

Using 'I' or 'i' in AppBrowser search ImageMagick.tcz, ImageMagick-doc.tcz, ImageMagick-dev.tcz doesn't appear on the hit list, but it is listed w/o filter.

[curaga]

The search data is updated nightly, IIRC.

[bmarkus]

The search data is updated nightly, IIRC.

ImageMagick is in the repo since 2010 or something like that. Don't think issue is related to the frequency of update but the update itself.

[maro]

... OSS installs OK but complains: depmod: ./kernel.tclocal: No such file or directory.

Is it something I should be concerned about? ...

The error message is a consequence of the fact that the 'OSS-modules-3.0.21-tinycore.tcz' extension "violates" the convention to have additional kernel modules in "/usr/local/lib/modules/$( uname -r)/kernel" (as it uses "/lib/modules/$( uname -r)/kernel" instead.

Now, 'kernel.tclocal' is a symbolic link in "/lib/modules/$( uname -r)" to "/usr/local/lib/modules/$( uname -r)/kernel". AFAIK this latter directory did exists in the initrd in the past, but this doesn't seem to be the case any more. Therefore the symbolic link points to a non existing directory, which causes the warning message. In my assessment this should not cause any problem, and any "non-violating" extension containing kernel modules will create this missing directory (and hence no further warning message should show up).

I had mentioned this "violation" in an earlier post, but I would not call it a "hanging offence". Nevertheless of the two obvious options to avoid this error message (i.e "fix" the OSS kernel module extensions, or add the directory again to the initrd) my vote would be for the former as it would be IMHO the "cleaner" way instead of the latter (which has the appeal to be the possibly easier one).

[curaga]

It would mean having to modify the scripts and possibly apps, and keep up those modifications for new OSS versions. Not something I would like to carry just for moving the module directory.