Tiny Core Base > Release Candidate Testing

tinycore_v3.0rc1

<< < (4/6) > >>

bmarkus:

--- Quote from: technosaurus on July 12, 2010, 11:12:59 AM ---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)

--- End quote ---

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.

tyler:
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

bmarkus:
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.

helasz:
I find the combination of squashfs and unionfs extremely useful. Do not you plan patching TC 3.0 kernel for unionfs?

curaga:
@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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page