Tiny Core Base > Release Candidate Testing
tinycore_v2.9rc4
meo:
Hi again Robert!
Just gave tinycore 2.9rc4 a test but it failed just as rc2 and rc3. I get the same error boot message about the sound as I mentioned in the tinycore 2.9rc3 thread and the sound (alsa) is muted when I load Xmms. Hope that others have better luck. I'll go back to tinycore 2.9rc1 since it's the only one that the sound works on.
Have fun keeping up your good work and don't feel gloomy because tinycore 2.9 will be a blast at last,
meo
jur:
At boot time I get segmentation fault and bus error.
This seems to go away if I use boot code 'base'. 'Norestore' has no effect other than not restoring, still seg fault and bus error.
I removed all extensions from OnBoot and tried again but same result.
[edit]: I still see the previously reported message about 'usleep: text file busy' before it disappears off the screen due to the other errors.
These errors happen during the time after checking boot codes, just after time zone and so on has been applied. When 'base' is used, this stage seems to be bypassed.
Question: Why is so much time spent on the rotating cursor when no extensions are loaded and boot code 'norestore' is used?
Juanito:
--- Quote from: danielibarnes on February 17, 2010, 05:24:21 PM ---I am preparing to release updates for the majority of my extensions. It seems that if I build them using 2.9 the new libc implies they may be incompatible with earlier releases. Should I build using 2.8.1 for maximum compatibility or is it the case that I need the new libc to fix problems (like exception support) that are currently lacking?
--- End quote ---
I would hold off for a couple of days yet.
The exception support comes from a recompiled libstdc++ in the base. Since this was significantly bigger than the previous libstdc++, we "sstripped" it, which means it will need to be overwritten by a "non-sstripped" version in order to compile against it. If the testing works out OK, the "non-sstripped" version and updated static libs, etc, will be added to base-dev.
In addition, the libc update may yet require some adjustment.
jur:
The /dev/shm permissions problem is still there, and I have just noticed that if I boot 'base' the permissions are correct.
roberts:
Booting base norestore is using ram. Loading extensions uses disk. When was the last time you fsck'ed? When was the last time you checksumed your extensions?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version