Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on July 11, 2010, 02:38:26 AM
-
Team Tiny Core is pleased to announce Tiny Core 3.0 RC1 is now available.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/tinycore_3.0rc1.iso
* New kernel update to 2.6.33.3 ( a upx'ed version is also available in the distribution file area ).
* New 64-bit kernel available in distribtion files area.
* New compressed swap in ram -> able to run more and longer, less crashes due to out of ram
* New tmpfs root always -> no longer possible to exhaust ram in an "embed" boot via files
* New improved virtualization support
* New ext4 support in base/base tools
* New delta extension updates as the default using zsync.
* New kernel for support of pci-hotplug modules
* New modules for eeepc-laptop and ssb
* New kernel-agnostic dep files supported by core functions.
* Updated busybox 1.17.0 New applets: flock, modinfo, rev, unxz, xz, xzcat. Tar etc support xz now.
* Updated glibc updated to 2.11.1 and recompiled against 2.6.33 kernel headers
* Updated gcc updated to 4.4.3, recompiled against 2.6.33 kernel headers and cloog, ppl, mpfr, gmp
* Updated e2fsprogs base libs/apps updated to 1.41.11
* Updated zlib 1.2.5, ncurses 5.7, sudo 1.7.2p6, pcmciautils 017, module-init-tools 3.11.1
* Updated util-linux-ng 2.1.7.2, libpng 0.43, libfreetype 2.3.12, libImlib2 1.4.4
* Updated X libs in base to Xorg 7.5, libICE-1.0.6, libSM-1.1.1, libX11-1.3.3, libXau-1.0.5, libXaw-1.0.7
* Updated libXcursor-1.1.10, libXdmcp-1.0.3, libXext-1.1.1, libXfont-1.4.1, libXft-2.1.14, libXi-1.3
* Updated libXinerama-1.1, libXmu-1.0.5, libXpm-3.5.8, libXrender-0.9.5, libXt-1.0.8, libXtst-1.1.0
* Updated libjepg, libsysfs, systool, get_device, bcrypt, rungetty
* Updated squashfs module with latest patch.
* Updated .profile for flwm titlebar new color.
* Updated tce-setdrive and tc-restore.sh for better /tmp/tce test.
* Updated 55-tc-rules for better permission on ramzswap.
* Updated tc-functions with new getMajorVer and getMirror
* Updated tce-audit, tce-fetch.sh, tce-load, tce-update, and appbrowser for getMirror.
* Updated tce-setup for microcore .gzs in /opt/tce remaster
* Updated ondemand, dropped jwm/wbar improved handling of multiple .desktop elements.
* Updated exittc to handle rare case of missing BACKUP env variable.
* Updated tc-config, tce-setup, startx, desktop.sh for legacy window manager support of freedesktop and ondemand.
* Updated AppsAudit: added OnDemand Maintenance (add/remove) OnDemand items.
* Updated ondemand to support new feature in AppsAudit.
* Updated AppsAudit: dropped full path from "Check for Updates" display.
* Updated flwm* for potential issue when used with peristent home
* Updated tce-setdrive to exclude cdrom and dvd.
* Updated mktclocal to exclude cdrom and dvd.
* Updated usbinstall moved bzImage and tinycore.gz/microcore.gz to /boot
* Updated wbar_upd_icon.sh for missing c: in freedesktop Terminal & Icon case.
* Fixed various typos and other small tweaks and adjustments
* Fixed freedesktopcheck in startx
* Updated usbinstall added UUID clause to waitusb option.
* Updated tce-update to acknowledge when system is up-to-date.
* Updated tce-update to accept tce dir as parameter.
* Fixed bug in tc-functions autoscan.
* Fixed flwm* ownership of .wmx files when alternate user is specified.
* Updated .filetool.lst & .xfiletool.lst to support alternate user(s).
* Updated tce-setdrive to suport alternate user.
* Updated shutdown.sh. Added .xfiletool.lst processing when home not in backup for persistent home.
* Updated cpanel. Dropped relic code referencing HOME.
* Updated tc-functions getMirror and getbasefile.
* Updated tce-load. Added for -i option, a fall through check of standard .tce_dir
* Updated tce-load. Fixed bug. Local loading was not processing all dependencies.
* Updated filetool.sh to explicitly call busybox tar.
* Updated tce-audit for recursive deletions.
* Updated appsaudit added "Clear Marked for Deletion" option.
* Updated desktop.sh, startx, tc-config to support generic icon manager via new interface files.
* Updated wbar with new interface files for new generic icon support.
* Updated getRGB for wallpaper recall current solid color background.
* Updated wallpaper to read current solid background color.
* Updated .xsession .X.d to allow spaces in filenames.
* Updated linstdc++ to 6.13 now aligns with toolchain extension.
* Updated rebuildfstab to support raid devices.
* Updated some incorrect device types and numbers.
* Updated fltk libs for threads, exceptions, and rtti support.
* Updated tc-config with new boot code blacklist
Note. Files likely in your backup that have changed and need to be updated:
opt/.filetool.lst
opt/.xfiletool.lst
opt/shutdown.sh
opt/tcemirror
Note:
.xsession likely in your backup update from /etc/skel.
wbar should be removed from .X.d/ as there is now a generic call to ICON manager in .xsession
Note: If you have been staying current and have alpha9 then the only changes from alpha9 to rc1 are:
* Updated fltk libs for threads, exceptions, and rtti support.
* Updated tc-config with new boot code blacklist
* Updated busybox 1.17.0 New applets: flock, modinfo, rev, unxz, xz, xzcat. Tar etc support xz now.
* Updated squashfs module with latest patch.
-
Please see my remarks re a Xorg-7.5 bug which has been traced to <what I understand to be> a i915 driver bug.
I understand drivers to be part of the kernel; so would this affect BzImage?
-
it seems that when x starts up (on plain tinycore, with no extensions) my display goes out of sync.
i'll have to dig into this and reverify.
using ati radeon x1300pro on pci-e. anybody else with an ati card can reproduce it?
-
@yoshi314:
There hasn't been a change w/ Xvesa in a while. My HD4350 and X1600 still work fine.
-
it seems it was a one-time problem. after a second attempt xvesa started and i had display.
btw, there is a small rectangle of garbage following my cursor on lxde2+xorg when i open some tinycore tool sub-dialogs or close them. it goes away after moving mouse cursor over to another program window. that's weird.
-
Hi yoshi314:
I wish to confirm the strange cursor behavior on lxde. I commented on it sometime ago. See:
http://forum.tinycorelinux.net/index.php?topic=3685.msg19361#msg19361
I see this behavior on fluxbox, xfce, and lxde. Not on gnome, flwm or icewm.
For this reason, I have remained on icewm rather than going to lxde.
Any suggestions much appreciated.
Thanks and Best Regards,
sci_fi
-
Hi all!
Just came home and saw that the first RC of TC 3.0 had arrived. After a first and brief try it works just fine with the original flwm. Thanks a lot to all of you who are a part of team TC! It will be exiting to follow the progress of TC 3.0 to it's final release. Thanks again!
Have fun improving TC,
meo
-
I have a question regarding the 64 bit kernel and Tinycore. I saw in the 3.0 Alpha 3 release notes that the tinycore64.gz was withdrawn due to a compatibility problem with Xvesa. With this in mind, is it possible to remaster Tinycore with the 64 bit kernel if Xorg is included, or is it only supported to use the 64 bit kernel with Microcore?
Thanks,
Brian
-
I have a question regarding the 64 bit kernel and Tinycore. I saw in the 3.0 Alpha 3 release notes that the tinycore64.gz was withdrawn due to a compatibility problem with Xvesa. With this in mind, is it possible to remaster Tinycore with the 64 bit kernel if Xorg is included, or is it only supported to use the 64 bit kernel with Microcore?
Thanks,
Brian
technically microcore + xorg + a desktop or a window manager is the same
-
I have a question regarding the 64 bit kernel and Tinycore. I saw in the 3.0 Alpha 3 release notes that the tinycore64.gz was withdrawn due to a compatibility problem with Xvesa. With this in mind, is it possible to remaster Tinycore with the 64 bit kernel if Xorg is included, or is it only supported to use the 64 bit kernel with Microcore?
Thanks,
Brian
technically microcore + xorg + a desktop or a window manager is the same
The reason I am asking specifically about Tinycore and the 64 bit kernel is because I am developing a program that simplifies remastering Tinycore and Microcore (http://forum.tinycorelinux.net/index.php?topic=6645.0 (http://forum.tinycorelinux.net/index.php?topic=6645.0)). I am adding in support to remaster with the 64 bit kernel, so I am trying to find out if the 64 bit kernel only works with Microcore or if it is possible/supported to remaster Tinycore with the 64 bit kernel if Xorg is included.
Thanks,
Brian
-
ok, i am a bit confused, because i cannot find root shell anywhere.
how do i get it? i need it to mount my encrypted lvm
edit: ok, looks like i can do it with sudo, which allows tc for everything without a password.
edit: extra filesystem modules (from filesystems package) are installed into /usr/local/lib/modules/2.6.33.3-tinycore . is that really correct?
edit3: where's ext4?figured it out, looks to be built-in.
edit4:
tc@box:~$ sudo alsaconf
Can't create temp file, exiting...
-
I have a question regarding the 64 bit kernel and Tinycore. I saw in the 3.0 Alpha 3 release notes that the tinycore64.gz was withdrawn due to a compatibility problem with Xvesa. With this in mind, is it possible to remaster Tinycore with the 64 bit kernel if Xorg is included, or is it only supported to use the 64 bit kernel with Microcore?
Thanks,
Brian
technically microcore + xorg + a desktop or a window manager is the same
The reason I am asking specifically about Tinycore and the 64 bit kernel is because I am developing a program that simplifies remastering Tinycore and Microcore (http://forum.tinycorelinux.net/index.php?topic=6645.0 (http://forum.tinycorelinux.net/index.php?topic=6645.0)). I am adding in support to remaster with the 64 bit kernel, so I am trying to find out if the 64 bit kernel only works with Microcore or if it is possible/supported to remaster Tinycore with the 64 bit kernel if Xorg is included.
Thanks,
Brian
so what you need to do is:
tinycore64 with Xorg=microcore64+Xprogs+Xlibs+Xorg+flwm_topside
you can not use 64 bit kernel with tinycore.gz because of kernel modules
well maybe you can try replacing kernel modules from microcore64.gz into tinycore.gz
-
The reason I am asking specifically about Tinycore and the 64 bit kernel is because I am developing a program that simplifies remastering Tinycore and Microcore (http://forum.tinycorelinux.net/index.php?topic=6645.0 (http://forum.tinycorelinux.net/index.php?topic=6645.0)). I am adding in support to remaster with the 64 bit kernel, so I am trying to find out if the 64 bit kernel only works with Microcore or if it is possible/supported to remaster Tinycore with the 64 bit kernel if Xorg is included.
Thanks,
Brian
My opinion is that it would be an unnecessary hassle to first download microcore64.gz to get the modules, only to add them to the current image (ie, downloading again most of the base). The wizard could simply state that if a 64-bit result is desired, start with the 64-bit image.
Yes, TC = MC + Xlibs + Xprogs + Xvesa (+flwm_topside+wbar). There's no difference beyond that, so just replacing Xvesa with Xorg in that equation lets things work.
Sure, it would also be possible to download the 64-bit kernel plus modules from microcore64.gz, and add those to the current image.
-
ok, i am a bit confused, because i cannot find root shell anywhere.
how do i get it? i need it to mount my encrypted lvm
edit: ok, looks like i can do it with sudo, which allows tc for everything without a password.
sudo su
edit: extra filesystem modules (from filesystems package) are installed into /usr/local/lib/modules/2.6.33.3-tinycore . is that really correct?
Yes. That's where they were before as well?
-
ok, i am a bit confused, because i cannot find root shell anywhere.
how do i get it? i need it to mount my encrypted lvm
edit: ok, looks like i can do it with sudo, which allows tc for everything without a password.
sudo su
edit: extra filesystem modules (from filesystems package) are installed into /usr/local/lib/modules/2.6.33.3-tinycore . is that really correct?
Yes. That's where they were before as well?
not sure.
i guess i messed something up on the way. it all seems to work now. i had some problems loading those modules earlier, and i was expecting to see them at /lib/modules/(....)
-
As best as I can tell fldigi (the culprit behind the fltk recompile) does not require exceptions, just rtti and threads - the space savings is over 100kb ... unless other programs needed exceptions enabled in fltk. (Note that exceptions still needed to be enabled in fldigi, but did not require them to be enabled in the fltk library)
Possibly it is right. For sure fldigi itself must be compiled with exceptions, rtti and threads. I tested compilation against fltk libs with same options. fltk.tcz now is 1.56M in size. I would live fltk libs as it is now to be on the safe side.
-
Version 3.0 is looking good! The last few alpha releases have been running without problems, but then I ran into a glitch with Xorg 7.5 during a hard drive installation of RC 1.
The machine is a Sony PCG-C1VPK, one of the old Picturebook line with a Crusoe processor upgraded to a mighty 238 MB of RAM. Because of the oddball 1024x480 display, which Xvesa sees as 640x480, I've resigned myself to loading Xorg. And indeed the previous test installation (3.0 alpha 8) had run with Xorg 7.5 without any obvious problems.
For RC 1 I had updated the bzImage and tinycore.gz files and deleted my data and onboot.lst from /tce. After booting and updating the local extension copies, I figured it was time to load Xorg-7.5 and expand from the default 640x480 to 1024x480 again. Alas, after loading Xorg 7.5 via the GUI Apps tool, I wasn't able to exit to the command prompt to run xsetup.sh or startx. Neither the logout menu nor the old Ctl+Alt+Bksp exit had any effect. (The lack of effect of the latter wasn't surprising, as this was apparently an "improvement" in the stock Xorg behavior.)
What <em>did<em> work was rebooting, exiting from Xvesa's GUI display via the logout menu, and then installing ala the command line: tce-load -i Xorg-7.5.tcz; xsetup.sh ; startx.
Why the logout/exit to prompt option didn't work I don't know. It might be an obscure permissions glitch, as I use boot codes for both user and host rather than the defaults. Now that Xorg-7.5 is in my onboot.lst, however, it's not a problem -- Xorg lets me exit to the prompt and back again without incident.
I'm not sure if something changed with the library upgrade, or I just didn't catch it earlier because I'd been keeping the onboot.lst around from alpha to alpha. But there you go...
Cheers,
Tyler
-
On my development system all extensions are mounted. Actually I have 262 loop devices which is definitely more than 256 and everything is working fine. So it looks like we can forget this 256 limit.
:-*
BTW, I do not recall an explicit statement that it is working now. Last as I remember that Kernel wise OK, but we need as new busybox to support it.
-
I find the combination of squashfs and unionfs extremely useful. Do not you plan patching TC 3.0 kernel for unionfs?
-
@tyler
I'm guessing the exit applet thought you were running Xorg, and thus didn't try to kill Xvesa.
Why ctrl-alt-backspace didn't work in Xvesa, that I don't know. A temporary glitch I think.
On this questionable improvement, I've reverted the change in 7.5; ctrl-alt-backspace works great there.
@bmarkus
Dynamic loops are working since the busybox update to 1.17.0-git (and 1.17.0 stable in -rc1).
@helasz
No, unionfs/aufs is not planned.
-
Running Micro Core 3.0 TC1 + Xvesa + aewm + various extensions on my Eee PC 900. It works perfectly and it's amazingly fast.
I noted that the wireless driver for the 2.6.33 kernel is a bit slower than 2.6.29; not a big issue anyway.
Amazing work, thanks.
-
I have noticed OSS.tcz for 3.0 is different than the one used in 2.11.6. It has a dependency over 32 or 64 bits modules, depending on the kernel you are using, I suppose. This should be great, as it correctly download and install the right set of modules.
However, I found the sound of my Fujitsu-Siemens Liteline is no longer working. Have any module been stripped out in the new version? It works again when using 2.6.11.
I have separate /tce dirs for each version, which I rename during a base norestore boot, to avoid mixing repos. Then I reboot again into the chosen version.
-
@MakodFilu
It is a newer version, but all modules that built were included. Only two or three of the unmaintained drivers (in attic/) didn't build; can't recall right now which ones.
What's the sound card?
-
Hi all!
I just have a suggestion. I would like a change of the color that comes up in app browser when an application is loaded. The current yellow is a bit hard to distinguish and I would therefore suggest a change to blue, for example the blue with following hex number: 00:00:00:a1. I suggest this because my medical condition, called muscle arthritis that causes pain and fatigue which forces me to rest a lot, and from my bed it's a little bit hard to see when an application is ready for use because of the color. Thanks for a great distro!
Have fun moving ahead with TC,
meo
-
@curaga
According to osstest, it is a:
/dev/oss/oss_allegro0/pcm0 (audio engine 0): ESS Maestro3 (ESS1998)
-
@curaga
According to osstest, it is a:
/dev/oss/oss_allegro0/pcm0 (audio engine 0): ESS Maestro3 (ESS1998)
I'm afraid allegro was one of them, seeing as it's not included in the 4.2 module extensions. Since it's unmaintained and didn't even build, I guess you'll need alsa from now on.
-
Hi all!
I have another suggestion for TC 3.0. It would be nice to have some kind of progress bar that shows how an installation or download is doing. The best would be to have it in the appbrowser in the field that shows what is downloading. If the progress bar is blue (like I suggested earlier) then the color could switch to red for example when everything is finished. I think that would be great and hopefully others agree.
Have fun making TC reach even higher in the IT world,
meo