Tiny Core Base > Alpha Releases

Tiny Core v4.0 Alpha 2 Testing

(1/7) > >>

roberts:
Tiny Core 4.0 Alpha2 is available for public testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/4.x/x86/alpha/

Change log:

alpha1:
* 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 all the custom core utilities to use the new repository area:
   http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/

alpha2
* New loadcpufreq to handle module loading.
* Updated eglibc for 486/586 support.
* Updated busybox 1.19 with latest patches and fix for chpasswd segfault.
* Updated ondemand for console based extensions via Freedesktop Exec=cliorx prgname
* Adjusted .xsession to handle X startup failure.
* Adjusted .setbackground colors for wallpaper handling.

maro:
Good news, the two items I mentioned about 4.0a1 are resolved.

So, as was the case in the later stages of the TC 2.x phase a rebuild of the 'libc' resolved the 'Xvesa' failure when run in a QEMU VM with KQEMU. This seems to be somewhat connected with what is labeled as "486/586 support".

I wonder what it was exactly that was changed for the 'eglibc' rebuild. To know this might help me in the future if I stumble somewhere else over a similar issue again.

Juanito:

--- Quote from: maro on September 02, 2011, 04:26:00 AM ---I wonder what it was exactly that was changed for the 'eglibc' rebuild. To know this might help me in the future if I stumble somewhere else over a similar issue again.

--- End quote ---

The issue is that the eglibc documention seems to be incorrect as regards compiling for i486/i586 compatibility, "--host=i486-pc-linux-gnu --target=i486-pc-linux-gnu" was required, wheras the documentation stated only "--host=i486-pc-linux-gnu" was needed.

gerald_clark:
TC now works on Vortex86 SOC.
Also tested with MC, Xorg-7.4 and Xorg-7.5, and flwm_topside.

gerald_clark:
My mistake, nbd.ko.gz is present.

Busybox was apparently compiled without nbd-client.

I compiled a standalone nbd-client for testing, and now have boot option "nbd=server:port tce=nbd0" working.
The  problem I am now having is that powerdown kills nbd-client before /dev/nbd0 is umounted.

Navigation

[0] Message Index

[#] Next page