WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny Core 5.0 Alpha 4 Testing  (Read 20448 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9252
Tiny Core 5.0 Alpha 4 Testing
« on: July 20, 2013, 12:28:47 AM »
Tiny Core 5.0 Alpha4 is available for public testing:

http://repo.tinycorelinux.net/5.x/x86/release_candidates/

Changelog for 5.0 alpha1:
* kernel update to 3.8.10 with (u)efi boot enabled
* option to use vmlinuz + rootfs.gz + modules.gz or vmlinuz64 + rootfs.gz + modules64.gz (where boot loader permits)
* aterm, freetype, imlib2, jpeg and libpng factored out of Xlibs/Xprogs
* glibc updated to 2.17 and recompiled against 3.8.x kernel headers
* gcc updated to 4.7.2, recompiled against 3.8.x kernel headers and cloog, gmp, mpc, mpfr and ppl
* e2fsprogs base libs/apps updated to 1.42.7
* util-linux base libs/apps updated to 2.22.2
* scm extensions have been dropped from this release

Changelog for 5.0 alpha2:
* util-linux updated to 2.23.1 due to blkid problems with qemu
* /usr/sbin/fstype modified for new blkid output (supress "/dev/sda" type output in /etc/fstab and mount gui)

Changelog for 5.0 alpha3:
* fixed copy2fs bug with tc-load (thanks to Gerald Clark for reporting)

Changelog for 5.0 alpha4:
* localhost.local domain added to /etc/hosts, /usr/bin/sethostname for avahi compatibility/libcups printing
* 50-udev-default.rules adjusted to allow rw access to /dev/rfkill

feedback welcomed and appreciated

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9252
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #1 on: July 20, 2013, 01:13:37 AM »
'finally managed to get several long standing problems solved:

For several kernel versions usb headsets have been broken, but now mine at least seems to work

For several versions of blueman, bluez and pulseaudio there has been a conflict in audio.conf:

bluez/blueman require Enable=Socket
pulseaudio requires Disable=Socket

..using gnome-bluetooth's bluetooth-wizard, it now seems to be possible to pair and play music to bluetooth headphones (a2dp) with "Disable=Socket"

..and use pavucontrol to switch back and forth between the local audio card, bluetooth headphones and usb headset

Screenshot attached  :)

Offline aswjh

  • Jr. Member
  • **
  • Posts: 82
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #2 on: July 20, 2013, 02:10:47 AM »
tinycore GUI not work in VirtualBox?
« Last Edit: July 20, 2013, 02:16:02 AM by aswjh »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9252
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #3 on: July 20, 2013, 02:26:50 AM »
Sorry, but could explain in more detail what the problem is?

Offline aswjh

  • Jr. Member
  • **
  • Posts: 82
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #4 on: July 20, 2013, 02:38:17 AM »
I try to boot from tinycore iso in VirtualBox,cannt enter the gui desktop.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #5 on: July 20, 2013, 03:06:31 AM »
When you follow identical procedure uner 4.x, do you get different results?
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline aswjh

  • Jr. Member
  • **
  • Posts: 82
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #6 on: July 20, 2013, 03:14:01 AM »
tinycore 4.7.7 ok.

Offline uli

  • WikiUser
  • *
  • Posts: 6
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #7 on: July 20, 2013, 05:15:03 AM »
Seems to be an issue with Hyper-V (Windows 8 ) as well. Xvesa yields a black cross on black background only, for all screen resolutions tested. Though, virtual screen seems properly sized according to chosen resolution.

Xorg works well !

Offline nick65go

  • Full Member
  • ***
  • Posts: 153
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #8 on: July 20, 2013, 02:46:53 PM »
Hi, could you tell me which programs use some /lib/ libraries in core.gz ?
I do not wish to slow down the development process. My findings are here down.

I extracted the full structure from core.gz, then choroot inside like:
 $ sudo chroot . bin/busybox ash
I checked with # ls -alR / every binary simlinked or compiled executable from /bin, /sbin, /usr/bin, /usr/sbin
(to easy searching on another virgin core5.gz copy, I just deleted all busybox 1.20 simlinks from them, inserted a busybox 1.21 static linked with uclib, then run /usr/bin/busybox --install /bin; Now in /bin are only simlinks to busybox, except the blkid. In /sbin, /usr/bin, /usr/sbin are now only the core specific scripts, and some ext2fs programs. This work did not influence the results).

The same "cleaning" was done for /lib and /usr/lib and adjusted that all library are corect by running /sbin/ldconfig to update the cache:
/sbin/ldconfig: uClibc version
/lib:
   ld-linux.so.2 => ld-linux.so.2
   libpthread.so.0 => libpthread.so.0
   libc.so.6 => libc.so.6
*   libcrypt.so.1 => libcrypt.so.1
*   libutil.so.1 => libutil.so.1
*   libe2p.so.2 => libe2p.so.2
*   libext2fs.so.2 => libext2fs.so.2
*     libcom_err.so.2 => libcom_err.so.2
*   libblkid.so.1 => libblkid.so.1
*     libuuid.so.1 => libuuid.so.1
   libdl.so.2 => libdl.so.2
   librt.so.1 => librt.so.1
   libnss_files.so.2 => libnss_files.so.2
   libnss_dns.so.2 => libnss_dns.so.2
     libresolv.so.2 => libresolv.so.2
   libnss_compat.so.2 => libnss_compat.so.2
     libnsl.so.1 => libnsl.so.1
   libanl.so.1 => libanl.so.1
   libm.so.6 => libm.so.6   <--asked by libstdc++.so.6

/usr/lib:
?   libstdc++.so.6 => libstdc++.so.6
*   libsysfs.so.2 => libsysfs.so.2
*   libz.so.1 => libz.so.1
*   libgcc_s.so.1 => libgcc_s.so.1
   libsudo_noexec.so => libsudo_noexec.so
/usr/local/lib:

After manualy tested every /sbin, /usr/bin, /usr/sbin program, I identified by ldd /path/to/prog only some used libraries:
/usr/bin/blkid needs libblkid.so.1, libuuid.so.1, libgcc_s.so.1
/usr/bin/uuidgen needs libuuid.so.1, libgcc_s.so.1
/usr/bin/bcrypt needs libz.so.1
/usr/bin/systool needs libsysfs.so.2
/sbin/pccardctl needs libsysfs.so.2
/lib/udev/pcmcia-socket-startup needs libsysfs.so.2
/usr/bin/sudo needs libutil.so.1, libcrypt.so.1, libz.so.1, libgcc_s.so.1
/sbin/mke2fs (tune2fs, e2fsk) needs libext2fs.so.2, libe2p.so.2, libblkid.so.1, libuuid.so.1

The question: who does use the rest of the core libraries? Thanks in advance.
« Last Edit: July 20, 2013, 03:14:00 PM by nick65go »

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 6888
    • My Community Forum
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #9 on: July 20, 2013, 05:53:30 PM »
Right, bcrypt is not needed in the base and can be removed.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Online coreplayer2

  • Hero Member
  • *****
  • Posts: 2436
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #10 on: July 20, 2013, 07:52:19 PM »
Ok, for anyone interested or looking for headers needed to compile apps in TC-5 alpha, I put up a script which prep's the full sources in lieu of headers.  Maybe it'll be useful to someone

http://forum.tinycorelinux.net/index.php/topic,15680.msg91785.html#msg91785

have fun
« Last Edit: July 21, 2013, 02:18:47 AM by coreplayer2 »

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #11 on: July 20, 2013, 08:57:06 PM »
Hi, could you tell me which programs use some /lib/ libraries in core.gz ?
I do not wish to slow down the development process. My findings are here down.

It is not clear what you are about.
Do you imply you suspect or verified some particular difference between 4.x stable vs. 5 alpha?
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #12 on: July 20, 2013, 09:05:11 PM »
Right, bcrypt is not needed in the base and can be removed.

I think bcrypt is needed in base at least with boot code "protect".
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 6888
    • My Community Forum
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #13 on: July 20, 2013, 10:50:01 PM »
Right, bcrypt is not needed in the base and can be removed.

I think bcrypt is needed in base at least with boot code "protect".

Hmmm... Maybe you are right. I have never used 'protect'. BTW it is missing in piCore.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9461
Re: Tiny Core 5.0 Alpha 4 Testing
« Reply #14 on: July 21, 2013, 03:08:16 AM »
@nick65go

All the NSS libraries are dynamically loaded, so you can't determine them as unused via ldd. I think sudo also loads the sudo lib dynamically.
librt, libdl, libnsl, and libresolv may not be used in the base, as busybox has its own implementations, but they are very often used by extensions, such that close to all systems would have them loaded.

libanl, the glibc async DNS library, is the only rarely used one. Whether it makes sense to move into an extension at its small size, I don't know.
The only barriers that can stop you are the ones you create yourself.