Tiny Core Linux

Tiny Core Base => TCB News => Alpha Releases => Topic started by: roberts on June 21, 2010, 11:44:19 AM

Title: Tiny Core 3.0 Alpha 8 Testing
Post by: roberts on June 21, 2010, 11:44:19 AM
Tiny Core v3.0 Alpha8 is now posted at http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates

Change log for Alpha 8

* Cleanup of many system file permissions.
* Updated tce-audit for recursive deletions.
* Updated appsaudit added "Clear Marked for Deletion" option.

Note. Files likely in your backup that have changed permissions and need to be updated:

opt/.filetool.lst
opt/.xfiletool.lst
opt/tcemirror

Notes: When using the updated "Mark for Deletion" in Apps Audit, check by also using
"Display Marked for Deletion" and if needed/desired the new "Clear Marked for Deletion"
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: meo on June 22, 2010, 12:23:52 AM
TinyCore Team!

Everything seems to work just as it should so thank you for your effort i making TinyCore 3.0 progress. I guess that a RC is coming soon. One thing that I noticed that somewhat puzzled me is that the .filetool.lst file by default contains opt/backgrounds in TinyCore 2.11.5 but not so in TinyCore 3.0 ALPHA 8. Is there some reason for this? Thanks again!

Have fun developing TinyCore further,
meo
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: althalus on June 22, 2010, 07:11:31 PM
One thing I would like to see is a generalisation of the $ICONS/wbar stuff.

I am building/testing tablaunch, as it has auto-hide, something I sorely miss in wbar, and I'd like to be able to update it when a new extension is loaded. For my own setup, I can happily hack away at whatever part of TC to get it to do what I want, but that's not really practical for something I may submit for the repo later.

One solution could be a directory into which scripts of this nature could be dropped, and have /usr/bin/desktop.sh run the scripts in that dir, but I'm sure there are other ways to do so.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: curaga on June 23, 2010, 05:09:59 AM
@althalus: if you set the unfocused alpha to 0 (-falfa 0), it's invisible until a mouse over.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: althalus on June 23, 2010, 02:46:30 PM
I tried combining -falfa with -always-ontop to try and get the same behaviour as something that properly auto-hides, but unfortunately I get an ugly square of my background stop on top of any windows in wbar's way. Leaving out the -always-ontop still leaves wbar in the position of being stuck behind my windows where I can't use it. Unfortunately at this point in time, wbar still just doesn't cut it for me, at least not until it has a proper auto-hide feature, so I stand by my original request in this topic.

For now I've remastered TC and replaced the wbar_icon_upd.sh script with one that does the same for tablaunch, but I'd like to be able to submit tablaunch to the repo complete with a script to have it automatically update when new extensions are installed.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: bmarkus on June 24, 2010, 10:22:00 AM
This is not directly related to Alpha 8 but all versions. Alpha testing cycle is a good time to mention.

fltk library which comes with TC base is compiled with --disable-threads option which blocks certain applications (in my case fldigi) linking against it. I replaced libraries in base with libs compiled with --enable-threads. I got a slightly bigger libs but compilation error message

undefined reference to `Fl::lock()'

is gone. I kindly ask to update libs in base. It is just one application now, but there may be others requiring this option.  >:(
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: jur on June 24, 2010, 10:45:39 PM
I see the solid background color bug is still there.

For example, if I set the color to 0.345-0.491-0.667 (R-G-B), next time round it comes up with 0.346-0.440-0.001.

The blue always seems to be much smaller than the previously set value.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: bmarkus on June 25, 2010, 02:13:08 AM
It seems there is a problem with the development tool chain, see topic

http://forum.tinycorelinux.net/index.php?topic=6621.0
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: bmarkus on June 25, 2010, 04:04:21 AM
This is not directly related to Alpha 8 but all versions. Alpha testing cycle is a good time to mention.

fltk library which comes with TC base is compiled with --disable-threads option which blocks certain applications (in my case fldigi) linking against it. I replaced libraries in base with libs compiled with --enable-threads. I got a slightly bigger libs but compilation error message

undefined reference to `Fl::lock()'

is gone. I kindly ask to update libs in base. It is just one application now, but there may be others requiring this option.  >:(

Well, one possible solution is to have these libs available in a tcz extension, for example the current fltk-xft.tcz  compiled with threads not to increase number of fltk variations. Anyhow, base would be better  ;)
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: roberts on June 25, 2010, 11:58:09 AM
I see the solid background color bug is still there.

For example, if I set the color to 0.345-0.491-0.667 (R-G-B), next time round it comes up with 0.346-0.440-0.001.

The blue always seems to be much smaller than the previously set value.
Got it fixed.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: roberts on June 26, 2010, 07:03:00 PM
I tried combining -falfa with -always-ontop to try and get the same behaviour as something that properly auto-hides, but unfortunately I get an ugly square of my background stop on top of any windows in wbar's way. Leaving out the -always-ontop still leaves wbar in the position of being stuck behind my windows where I can't use it. Unfortunately at this point in time, wbar still just doesn't cut it for me, at least not until it has a proper auto-hide feature, so I stand by my original request in this topic.

For now I've remastered TC and replaced the wbar_icon_upd.sh script with one that does the same for tablaunch, but I'd like to be able to submit tablaunch to the repo complete with a script to have it automatically update when new extensions are installed.

I am implementing generic support for icon manager like that of desktop window manager.
You will be able to have tablaunch function like wbar.  Fully supported.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: althalus on June 27, 2010, 01:19:53 AM
I am implementing generic support for icon manager like that of desktop window manager.
You will be able to have tablaunch function like wbar.  Fully supported.
Again, many thanks.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: curaga on June 27, 2010, 03:48:18 AM
Looks like the libpng.so symlink changed between alpha7 and 8. I don't think this should've happened; it should still point to libpng12.so, not to libpng.so.3 as it now does.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: meo on June 28, 2010, 10:07:13 AM
Hi all!

Just wanted to mention that clamav seems to need some fixing to work with tinycore 3.0. After issuing the command: freshclam I get the following error message: ERROR: Can't open/parse the config file /usr/local/etc/clamav/freshclam.conf and that also is the case using sudo.

Have fun making TinyCore progress,
meo
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Jason W on June 28, 2010, 01:44:13 PM
Clamav:  likely just an extension issue, I will look into it.

Thanks for reporting but please open a thread in the TCE Bugs section for any further discussion on it.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: SvOlli on June 28, 2010, 02:02:38 PM
Please also note, that there's been a fix against a vulnerability for libpng release three days ago.
This vulnerability has been assigned ID CVE-2010-1205 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1205).

Source: http://www.libpng.org/pub/png/libpng.html

I think this calls for an update of libpng.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: meo on June 28, 2010, 02:07:57 PM
Hi Jason!

I wasn't sure where to post it so I did it where comments are made on the cut of tinycore that I discovered it. Won't happen again.

Have fun and keep up your good work,
meo
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: meo on June 28, 2010, 02:11:35 PM
Hi again Jason!

I wasn't sure where to post it so I did it in the thread that is discussing the cut of tinycore where I discovered it. It won't happen again. Sorry!

Have fun and keep up your good work,
meo
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Jason W on June 28, 2010, 02:42:15 PM
Hey meo,

No big deal.  But even if it is suspected that an issue with an extension is related to changes in the base, it keeps the TCB release thread cleaner to post it in the TCE Bugs area.  If it is found that the issue with the extension is caused by a change or issue in base, then a mention of it can be made here.

Thanks.

Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: robc on June 30, 2010, 10:20:20 AM
I'm having trouble getting my PS/2 mouse to work with 3.x. I attached the messages log from syslog. It looks like this is what is said about the problem:
Quote
May 15 00:30:49 (none) user.info kernel: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
May 15 00:30:49 (none) user.warn kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS?
May 15 00:30:49 (none) user.warn kernel: If AUX port is really absent please use the 'i8042.noaux' option.

Edit: this is on a base norestore boot
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: roberts on June 30, 2010, 03:50:41 PM
Looks like the libpng.so symlink changed between alpha7 and 8. I don't think this should've happened; it should still point to libpng12.so, not to libpng.so.3 as it now does.
Will be fine in alpha nine.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: curaga on July 01, 2010, 03:15:00 AM
@robc:

Try the options i8042.reset and i8042.nopnp (separately and together). If still nothing, and it works in earlier kernels, please boot with i8042.debug and post a bug report to the kernel bugzilla.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Juanito on July 01, 2010, 06:50:17 AM
It seems there is a problem with the development tool chain, see topic

http://forum.tinycorelinux.net/index.php?topic=6621.0

In fact not the development tool chain but libstdc++.so.6.0.9 in the base should be libstdc++.so.6.0.13...
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: robc on July 01, 2010, 11:02:52 AM
@robc:

Try the options i8042.reset and i8042.nopnp (separately and together). If still nothing, and it works in earlier kernels, please boot with i8042.debug and post a bug report to the kernel bugzilla.
Thanks for the suggestion. reset, nopnp, and noaux had no affect of the function of the mouse even though noaux cleared the failure message. The PS/2 mouse isn't too much of an problem for me since I will only be using USB devices.

A bigger problem is when I exit X I can only see a few characters in the prompt. They are not always the same, sometimes I can only see the "y" character, other times its only "t". Sometimes I can see everything but after issuing a few commands all but a few characters disappear... ???

If I boot with the text bootcode then the prompt is ok and acts normally. It only has this problem after X has been started. This happens with either Xvesa of Xorg without 3d, when the Xorg-7.5-3d extension is loaded then everything works fine... :-\ I guess I'll have to use Xorg with this board, also I tried using Xorg -configure as stated in the info file but this resulted in a segmentation fault and gave an unusable conf file, so I tried the vesa one that was included and that seemed to work. I attached the Xorg.0.log with the seg fault.

I tried 2.11.4 on this board and looks like these problems are present there also.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: gutmensch on July 03, 2010, 01:32:24 AM
I think another busybox update would be nice for some good reasons, just tested 1.17.0 from git and found:

1. resolved losetup bug showing only loop devices till /dev/loop9 and additionally not showing any free loop devices behind that (VERY annoying, still in tc 2.11.x and 3.0ay)
2. resolved mktemp behaviour to create tmp files "somewhere" but now in /tmp/ like in coreutils
3. minor code shrinks during the last weeks (wanna make tc smaller and smaller, eh?)

Best regards,
Robert
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: curaga on July 03, 2010, 02:38:24 AM
I think another busybox update would be nice for some good reasons, just tested 1.17.0 from git and found:

1. resolved losetup bug showing only loop devices till /dev/loop9 and additionally not showing any free loop devices behind that (VERY annoying, still in tc 2.11.x and 3.0ay)
2. resolved mktemp behaviour to create tmp files "somewhere" but now in /tmp/ like in coreutils
3. minor code shrinks during the last weeks (wanna make tc smaller and smaller, eh?)

Best regards,
Robert

We're aware ;)
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: vinnie on July 03, 2010, 08:18:30 AM
Ok, installing software after removing the pen where there microcore cause the package is installed without the dependencies (and obviously does not work).
With the pen mounted still works perfectly.
The old version not have the problem.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Xianwen Chen on July 03, 2010, 11:04:04 AM
Tiny Core v3.0 Alpha8 is now posted at http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates

Change log for Alpha 8

* Cleanup of many system file permissions.
* Updated tce-audit for recursive deletions.
* Updated appsaudit added "Clear Marked for Deletion" option.

Note. Files likely in your backup that have changed permissions and need to be updated:

opt/.filetool.lst
opt/.xfiletool.lst
opt/tcemirror

Notes: When using the updated "Mark for Deletion" in Apps Audit, check by also using
"Display Marked for Deletion" and if needed/desired the new "Clear Marked for Deletion"

I'm not sure if this is a bug Xorg, graphics, or TCL 3 Alpha 8. However, a screenshot is taken. It could be worse that the whole screen is blurred.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: vinnie on July 03, 2010, 11:22:28 AM
Ok, installing software after removing the pen where there microcore cause the package is installed without the dependencies (and obviously does not work).
With the pen mounted still works perfectly.
The old version not have the problem.

Modifying the content of the file / opt / .tce_dir (with a tmp dir for example) everything works fine.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: neonix on July 03, 2010, 01:26:19 PM
I can't mount MMC or SD card in 3.x, Kingston DataTraveler pendrive works fine. I don't even know how to investigate this problem.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: curaga on July 03, 2010, 02:18:22 PM
@Xianwen Chen: Xorg.0.log and dmesg please. If this is an Intel chip, try disabling framebuffer compression in xorg.conf.

@neonix: dmesg, device name, can you mount manually?
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: neonix on July 03, 2010, 08:58:08 PM
@neonix: dmesg, device name, can you mount manually?
dmesg doesn't show any errors. I can't mount manually because /mnt is empty.
Code: [Select]
scsi 0:0:0:0: Direct-Access     USB 2.0  SD MMC Reader         PQ: 0 ANSI: 0 CCS
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 62720 512-byte logical blocks: (32.1 MB/30.6 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda:
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: maro on July 03, 2010, 09:36:56 PM
neonix: Are you sure that there is a partition on the device? Maybe a fdisk -l /dev/sda and blkid /dev/sda* can provide some insight.
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Xianwen Chen on July 04, 2010, 06:14:23 AM
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Xianwen Chen on July 04, 2010, 06:15:10 AM
@Xianwen Chen: Xorg.0.log and dmesg please. If this is an Intel chip, try disabling framebuffer compression in xorg.conf.

@neonix: dmesg, device name, can you mount manually?

Hi curaga,

Thanks a lot! I've falled back to 2.11.6 because stability is crucial to me.

Best regards,

Xianwen
Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: roberts on July 04, 2010, 06:36:35 AM
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen
Check for an update to an extension proper is based on md5 change.
Dependencies are handled via appsaudit "Check for Missing Dependencies" as it updates all .dep files.

Title: Re: Tiny Core 3.0 Alpha 8 Testing
Post by: Xianwen Chen on July 04, 2010, 06:40:47 AM
Hi Robert,

When updating TCE, does the script check .dep file? What I have experienced is that the script only checked md5 sum files. For example, wireless_tools.tcz in 2.x and 3.x have the same md5sum, but with different dependencies. This can mix up the TCE for different major versions without warning users.

Best regards,

Xianwen
Check for an update to an extension proper is based on md5 change.
Dependencies are handled via appsaudit "Check for Missing Dependencies" as it updates all .dep files.



Hi Roberts,

I see. Thanks a lot for clarification!

Would it be possible to add dependency check to the update script? I believe that it is necessary.

Best regards,

Xianwen